Real-time SEC 8-K material event filings for any ticker. (x402: 0.001 USDC per call)
HTTP equivalent: GET /x402/sec-8-k-real-time-filings Payment: x402 protocol — send X-PAYMENT header with base64 payment payload, or X-API-Key / X-Owner-Key / Bearer token to bypass.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide only a title, so the description carries the full burden. It discloses the x402 payment requirement, cost per call, and authentication methods (X-PAYMENT header, API keys/bearer token), which are important behavioral details beyond the empty schema. However, it does not describe the response format or other limitations.
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 three sentences: purpose, HTTP equivalent, and payment/auth. It is front-loaded with the core purpose and contains no superfluous content. Every sentence 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?
The tool description lacks guidance on how to pass the ticker symbol, and there is no output schema to clarify the return structure. Given the absence of schema and annotations, the description is not fully self-contained for an agent to invoke the tool correctly.
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 input schema is empty with no defined parameters, but the description mentions 'any ticker' without explaining how to specify the ticker. Since additionalProperties is true, an agent may guess, but the lack of explicit parameter documentation is a gap. The baseline for 0 params would be 4, but the implied parameter reduces the score.
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 explicitly states it provides real-time SEC 8-K filings for any ticker, using a specific verb ('filings') and resource, distinguishing it from sibling SEC tools like sec_10_k_annual_filing and sec_10_q_quarterly_filing.
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 implies usage for 8-K filings via the tool's name and wording, but it does not explicitly state when to use this tool versus alternatives or mention sibling tools. The context is clear but lacks direct comparisons or exclusions.
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.
Multiple tool pairs are exact duplicates (e.g., wallet_analysis/wallet_analyzer, honeypot_check/rugpull_detector, defi_yield/defi_yield_rates) with identical descriptions, and many overlapping scanners (squeeze_scanner variants). An agent cannot reliably distinguish these tools.
Names are all snake_case, but conventions vary wildly: some are resource names (btc_price), some are actions (list_magnets), some are generic utilities (calculator), and duplicates use different naming patterns for the same function (wallet_analysis vs wallet_analyzer). No consistent verb_noun or resource_action pattern.
139 tools is an extreme count for any MCP server, far exceeding the 50+ threshold. The scope is a grab-bag of unrelated domains (crypto, FDA, SEC, utilities, web scraping), suggesting no curation.
The set is a shallow pile of read-only queries and utilities with no lifecycle management for any one domain. Many sub-areas have only one or two tools, and duplicates occupy slots where distinct operations should be. The lack of a clear domain makes completeness impossible to assess, but the surface is redundant rather than comprehensive.