x402_discovery
Free x402 discovery document (resources, prices, payTo, facilitator, convertLadder).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Money-Engine x402 Research
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the burden. It mentions the tool is 'free' but does not clarify if it's read-only, idempotent, or has side effects. However, the input schema has no parameters, implying a straightforward retrieval.
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 sentence that conveys the essential information without unnecessary words.
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?
Given no parameters and no output schema, the description adequately specifies what the tool returns. However, it could mention the format or that the document is read-only.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so schema description coverage is 100%. The description adds value by enumerating the document's contents beyond the empty schema.
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 specifies the tool returns a 'discovery document' and lists its contents (resources, prices, etc.). The verb 'Free' is ambiguous but the overall purpose is clear and distinct from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like x402_health or x402_research_brief. The description only states what it does.
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.
TDQS
B3.4/5.0
Disambiguation4/5
Each tool has a distinct primary purpose (discovery, health, free sample, paid outline, paid brief, alternative scrub), but the conversion ladder is mentioned in multiple tools, which could cause slight confusion for an agent about which free tool leads where.
Naming Consistency5/5
All tools consistently use the 'x402_' prefix followed by a descriptive compound noun (e.g., discovery, health, research_brief, sample_outline), creating a predictable and clear naming pattern.
Tool Count5/5
With 6 tools, the set is well-scoped for a research API with a free-to-paid conversion ladder, covering all necessary stages without superfluous or missing tools.
Completeness4/5
The tools cover the complete research generation flow (discovery, health check, free sample, paid outline, paid brief), with an alternative scrub demo. A minor gap is the absence of a history or status tool for previously generated research.