team.management WebMCP audit

Rescan
audited Sep 5, 2026in 13s
80/ 100100% of the applicable check weight evaluated

2 tools registered. Strongest in shared experience, weakest in trust.

Shared experience100
Tool selection100
Tool quality100
Trust0
https://team.management
Captured view of https://team.management

Tools

0 read, 0 write, 2 undeclared
Loading map
search_docs: fail

search_docs

Search the team.management documentation, protocols, and comparisons. Returns the most relevant sections with links.No behaviour hints declared. Agents should treat it as possibly state-changing.
pagehttps://team.management/
implementation
viaimperative
entry pointdocument
registered after180ms
executepresent
api surface
queryrequired
annotations
read onlynot declared
untrusted contentnot declared
titlenot declared
1 finding
failAnnotations present
weight 5
2 of 2 read-shaped tools do not declare readOnlyHint: true, so an agent has to treat them as possible writes and ask before calling. (Declaring readOnlyHint: false earns nothing - it is the default.)
search_docs, get_page
fix
{
  name: "search_docs",
  // Declare readOnlyHint: true on tools that truly have no side effects -
  // that is the claim that lets an agent relax confirmation on reads.
  // (false is the default, so declaring it adds no information.)
  annotations: { readOnlyHint: true }
}
tool json
{
  "name": "search_docs",
  "description": "Search the team.management documentation, protocols, and comparisons. Returns the most relevant sections with links.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Natural-language search query, e.g. 'how does DAIC enforcement work'"
      }
    },
    "required": [
      "query"
    ]
  },
  "annotations": {}
}
Showing search_docs

Findings

Shared experience

100 / 100 · weight 30
not applicableVisible effect
weight 6
Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.
passPage experience
weight 16
The page a person sees holds up next to the agent surface: a working interface, visible actions, readable content, nothing in the way.
passHuman parity
weight 8
The person co-browsing can see and use this page - the same page the agent's tools act on.

Tool selection

100 / 100 · weight 25
not applicableInvoke success rate
weight 6
Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.
passTool selection
weight 12
An agent chose an existing, callable tool and built a schema-valid call for all 2 canonical intents, each matching the kind of tool its intent needs. Nothing was executed, so this verifies selection, not outcomes.
not applicableCoverage vs. site type
weight 7
This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Tool quality

100 / 100 · weight 25
passRegistration timing
weight 1
Every measured tool registered within 180ms of navigation.
toolget_page
passCanonical entry point
weight 3
All 2 tools register on the canonical document.modelContext entry point.
passSchema validity
weight 4
All 2 declared input schemas are structurally valid object schemas.
passSchema quality
weight 4
All 2 tool schemas describe their parameters, and every description stays within Chrome's size guidance.
passNaming quality
weight 2
All 2 tool names are consistent, verb-led, and within Chrome's size guidance.
passStub detection
weight 4
All 2 tools declare an execute handler.
passRegistration errors
weight 2
No tool registration threw during the capture.
passDescription quality
weight 5
All 2 rated tool descriptions say what the tool does, when to use it, and what it returns.

Trust

0 / 100 · weight 20
failAnnotations present
weight 5
2 of 2 read-shaped tools do not declare readOnlyHint: true, so an agent has to treat them as possible writes and ask before calling. (Declaring readOnlyHint: false earns nothing - it is the default.)
toolsearch_docs
search_docs, get_page
fix
{
  name: "search_docs",
  // Declare readOnlyHint: true on tools that truly have no side effects -
  // that is the claim that lets an agent relax confirmation on reads.
  // (false is the default, so declaring it adds no information.)
  annotations: { readOnlyHint: true }
}
not applicableAnnotation mismatch
weight 5
No tool declares a readOnlyHint, so there is no safety claim to contradict.
not applicableUntrusted content hint
weight 3
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
not applicableHint vs. observed
weight 4
Not invoked on this run: this audit did not call any tool. Scheduled re-audits only read the registry; a live audit from the report page calls the tools that declare readOnlyHint: true.
not applicableInjection surface
weight 3
No tool's metadata carries instruction-shaped text aimed at the agent reading it. This check only ever flags; it never credits a site.

Tool selection

100% across 2 intents
I want to search docs on this site.ok
chosesearch_docsexpected search docskind matched
arguments
{
  "query": ""
}
I want to get page on this site.ok
choseget_pageexpected get pagekind matched
arguments
{
  "path": ""
}
model: gemini-2.5-flash

Add the tools this site is missing

Our scanner reads your website and suggests the right WebMCP tools for it.
Reads the site's public pages; takes a few seconds.
The open source webmcp plugin teaches your coding agent to audit a site, implement tools on document.modelContext, and verify them in a real browser. npx @ora-ai/webmcp-verify runs the verification on its own. No signup, no hosted service.
how this was captured
observed via
capture shim (Chromium 151.0.7922.34)
chrome
151.0.7922.34
capture shim
v3
spec snapshot
2026-08-26
mode
fast
pages
1 - entry page only
tools
2
invoked
not invoked; a live audit calls them
run time
13s
finished
Sep 5, 2026
Checked the way in-browser agents discover tools: the top-level document's modelContext registry, read after the page settles.
Listed in the community directory.