Scan a URL for agent capabilities and payment protocols. Returns full results including x402, MPP, L402, discovery, bazaar, MCP, plugins, OpenAPI, and more.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to scan (http or https) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says it scans and returns results; it does not disclose that this involves network access to the URL, potential delays, privacy implications, or what happens on inaccessible/invalid URLs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that immediately states the tool's purpose, then provides a concise list of included result types. Every part earns its place with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter scanning tool with no output schema, the description gives the essential purpose and a useful list of what is included in the results. It lacks deeper details on output structure or error/edge-case behavior, but for the given complexity it is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage for the single parameter is 100% and the parameter description ('URL to scan (http or https)') already conveys the meaning. The tool description adds context about the scan scope (capabilities and payment protocols) but does not add new parameter-specific semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('Scan') on a specific resource ('URL') and enumerates the return content (x402, MPP, L402, discovery, bazaar, MCP, plugins, OpenAPI). The phrase 'full results' also helps differentiate from the likely abbreviated sibling 'scan_compact'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit or implicit guidance about when to use this tool vs. alternatives. Sibling tools like get_history and scan_compact are not mentioned, and though 'full results' hints at a contrast, there is no clear when-to-use or when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are largely distinct: scan_url and scan_compact both scan but differ in output detail and purpose, which could cause slight confusion. get_history and validate_x402_json are clearly separate. Overall, descriptions resolve most ambiguity.
All tool names use snake_case and follow a predictable verb_noun pattern: get_history, scan_url, validate_x402_json. scan_compact slightly deviates as verb_adjective but still fits the pattern well.
With only 4 tools, the server is tightly scoped to its purpose—scanning URLs, validating x402 JSON, and retrieving history. Each tool serves a clear need without unnecessary bloat.
The tool set covers the full workflow: scanning (full and compact), validation, and historical access. There are no obvious dead ends—agents can scan, validate, and review past scans without missing functionality.
