Max-pain strike + put/call open-interest ratio for an expiry — the price level where option holders lose most; a positioning/magnet signal. Send { currency, expiry? }. [x402 paid tool — price $0.005; POST /api/options/maxpain]
| Name | Required | Description | Default |
|---|---|---|---|
| expiry | No | e.g. 28AUG26 | |
| currency | Yes | BTC, ETH, or SOL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses the paid cost ($0.005) and endpoint (POST), but does not state if the tool is read-only, has destructive side effects, or data freshness guarantees. Adequate but incomplete.
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?
Extremely concise: two sentences define purpose and input, plus a compact note on cost and endpoint. No wasted words; information is front-loaded.
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 paid financial tool with no output schema, the description covers the output (max-pain strike + ratio), input, cost, and endpoint. Missing explicit output structure details, but remains adequate for agent invocation.
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 covers both parameters with descriptions (e.g., 'BTC, ETH, or SOL' for currency). The description merely restates input format without adding new meaning beyond the schema. Baseline score of 3 applies due to high schema coverage.
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 it provides 'Max-pain strike + put/call open-interest ratio' and defines max-pain as the price level where option holders lose most. This distinguishes it from sibling tools like options_chain or options_greeks, which serve different purposes.
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?
Description specifies input format ('Send { currency, expiry? }') but does not provide guidance on when to use this tool versus alternatives, nor any exclusions. The paid nature is noted, but no explicit context for optimal use.
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.
Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.
All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.
With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.
The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.