x402_health
Free liveness + pricing for the money-engine Research API (x402 USDC on Base). Ladder: free sample_outline → outline 0.01 → brief 0.02.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Money-Engine x402 Research
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions 'free' and pricing ladder but does not disclose behavioral traits like potential side effects or authentication needs.
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?
Two concise sentences, though slightly ambiguous on what 'liveness' entails.
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?
Adequate given no parameters or output schema, but leaves detail gaps about the response format of liveness and pricing.
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?
No parameters exist; baseline score of 4 as description need not add meaning beyond the schema.
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 states 'Free liveness + pricing for the money-engine Research API' and mentions a ladder of tools, distinguishing it from siblings like x402_discovery and x402_research_brief.
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?
Implies use for checking liveness and pricing, but does not explicitly state when to use vs. alternatives or when not to use.
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.