Skip to main content
Glama

Verified capabilities of a site

list_verified_capabilities
Read-onlyIdempotent

What a domain declares agents can do (OpenAPI operations, MCP tools, A2A skills, API catalog entries), each classed by safety (read_only_public up to financial), and which ones CrawlCheck actually called and confirmed - plus every mismatch between declaration and behaviour. Only read-only public actions are ever called; everything else says why it was not. From the latest scan on file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "list_verified_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
verified_onlyNoReturn only the capabilities that were confirmed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the description's job is to add context, and it does: results come from the latest scan on file (not a live fetch), only read-only public actions are ever invoked, non-invoked capabilities explicitly report why they were skipped, and mismatches between declaration and behaviour are included. That is meaningful behavioral detail beyond the annotation set. It does not cover behavior when no scan exists for the domain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense but well-ordered statement: what is declared, how it is classed, what was confirmed, what mismatches exist, and the safety constraint on calling. No filler and no repetition of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-value burden, and it does by enumerating the capability categories, the safety classification range, verification status, and mismatch reporting. Missing is only the edge case of an unscanned or unknown domain, which is a small gap for a read-only listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: verified_only is documented in the schema, but domain has no description. The description says results come 'from the latest scan on file' for 'a domain', which hints that the domain must already have been scanned, but it never clarifies format (hostname vs URL) or what happens on a miss. Baseline 3 fits, since the description only marginally compensates for the undocumented required parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource and its contents precisely: capabilities declared by a domain (OpenAPI operations, MCP tools, A2A skills, API catalog entries), each safety-classed, plus which ones were actually called and confirmed, plus mismatches. An agent can tell this is a declared-vs-verified capability report, not a raw scan or a safety verdict. It stops short of naming the sibling tools it should be preferred over (check_site_safety, mcp_servers, field_check), so differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No sentence states when to use this versus alternatives, but 'From the latest scan on file' implicitly routes the agent: this reads cached scan output rather than triggering a new crawl (scan_domain). The scope of what is returned is clear enough that the use case is inferable, but there are no explicit exclusions or sibling pointers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.