Skip to main content
Glama
Sign In

Agentry — The Trust Layer for the Agent Economy

by io.github.cthulhutoo
OverviewDiscussionsAdmin

trigger_scan_api_scanner_scan_post

Trigger Scan

Scan domains for A2A Agent Card discovery.

Checks the given domains for /.well-known/agent.json endpoints and extracts agent capability metadata. Results are stored and can be retrieved via the scan results endpoint.

Responses:

202: Successful Response (Success Response) Content-Type: application/json

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": {
      "domains": "<domains>"
    },
    "name": "trigger_scan_api_scanner_scan_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes

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?

With no annotations provided, the description carries the full burden. It clearly discloses that the tool performs a network scan, extracts metadata, and stores results. It also mentions the 202 response, suggesting asynchronous acceptance. It lacks details on side effects or auth, but the stored-results behavior and endpoint check are transparent enough for a trigger tool.

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

Conciseness4/5

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

The description is concise and front-loaded with the primary action, followed by a brief explanation and a response section. Every sentence adds value, but the response section is minimal and could be integrated more neatly. Overall, it is well-structured and not bloated.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the description covers the core action and storage behavior. However, it omits details about asynchronous execution (implied by 202 but not stated) and what the response body contains. This leaves the agent uncertain about the immediate return value and follow-up sequence, so completeness is moderate.

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?

The schema has one parameter 'domains' with 0% coverage. The description adds meaning by clarifying that domains are checked for /.well-known/agent.json, implying each string is a base domain. However, it does not specify domain format (e.g., with or without scheme, trailing slash), leaving some ambiguity.

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

Purpose5/5

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

The description opens with a specific verb+resource: "Scan domains for A2A Agent Card discovery," and elaborates by checking for /.well-known/agent.json and extracting capability metadata. It clearly distinguishes from sibling tools like trigger_discovery_cycle and get_scan_results by stating it operates on given domains and stores results.

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?

The description implies usage context by stating it scans domains and that results can be retrieved later via the scan results endpoint. However, it does not explicitly contrast with alternatives like trigger_discovery_cycle or state when not to use this tool, so the guidance remains implied rather than explicit.

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

All Agentry — The Trust Layer for the Agent Economy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources