List every apix402 check an agent can buy: route, price in USDC, what question it answers, and its free preview. Start here. Payment is x402 over plain HTTP -- no API key, no account, the wallet is the identity.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral transparency burden. It discloses the payment mechanism (x402 over HTTP), the lack of API key/account requirements, and that a wallet serves as identity. It does not explicitly state that the tool is read-only, but the verb 'List' strongly implies a non-destructive operation.
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 two sentences with no filler. The first sentence front-loads the core function and output fields; the second adds essential payment/auth context. Every word earns its place.
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 zero-parameter catalog tool with no output schema, the description is complete: it lists what the tool returns (route, price, question, preview), how to use it (start here), and the payment/auth model. No critical context is missing.
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?
The tool has zero parameters, and the schema coverage is 100% trivially. The baseline for zero-parameter tools is 4, and the description reinforces that no filters are needed by stating it lists every check.
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 the tool lists all apix402 checks available for purchase, including route, price, question, and free preview. The verb 'List' and specific resource make the purpose unambiguous, distinguishing it from the sibling sample-check tools.
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 phrase 'Start here' explicitly instructs users to invoke this tool first when browsing available checks. It does not name alternatives, but the context of sibling tools being individual checks implies this is the discovery entry point.
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.
Each tool targets a distinct financial check (DAO governance, lending depeg, oracle staleness, Safe authority, vesting status), and the catalog serves as the index. No two tools overlap in purpose or output.
Five tools follow a clear 'noun_sample' pattern, but the catalog breaks the pattern with a prefixed name 'apix402_catalog', creating a minor inconsistency. Still, all names are snake_case and readable, so the deviation is small.
With only 6 tools, the set is compact and each tool represents a specific sample category plus a catalog entry point. This is an appropriate size for a preview-oriented MCP server.
The catalog lists all available checks, and the five samples cover key verticals (governance, lending, oracles, safe custody, vesting). The only gap is that paid endpoints are not exposed as MCP tools, but that is by design since payment occurs over HTTP.