ipo_pipelineNew S-1 and F-1 registration statements as they land at EDGAR, market-wide and newest first: the earliest public signal of a US IPO. Costs $0.01 per call.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Filings to return, max 40. Default 20. | |
| include_amendments | No | Also include S-1/A and F-1/A. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint annotation, the description discloses a per-call cost of $0.01, states the ordering ('newest first'), and indicates the scope ('market-wide'). These add practical behavioral context not covered by annotations, though it does not mention pagination or rate limits.
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 redundant information. It front-loads the core purpose and adds a critical cost note, making it concise and well-structured.
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 is simple with optional parameters, and the description covers the main use case and key details like ordering and scope. Since there is no output schema, the description does not describe return fields, but for a listing tool this is acceptable; the context is sufficient for an agent to decide whether to invoke it.
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 description coverage is 100% for both parameters, and the description does not add new semantic meaning beyond what the schema already provides. The mention of 'newest first' is a tool-level behavior, not parameter-specific, so the baseline of 3 is appropriate.
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 new S-1 and F-1 IPO registration statements from EDGAR, market-wide and newest first, specifically calling it the 'earliest public signal' of a US IPO. This is specific and distinguishes it from general filing tools like latest_filings or recent_filings.
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 tracking new IPO filings but does not explicitly mention when to use this over alternatives or when not to use it. It provides context ('market-wide, newest first') but lacks direct comparison with sibling tools, so guidance is only implied.
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.
Most tools have clearly written descriptions, but several pairs overlap semantically: token_price/token_report, latest_filings/recent_filings, and institutional_holdings/who_holds/activist_stakes all require careful reading to pick the right one. The overlap is not severe enough for a 2, but it is still more than the occasional confusion.
Names are consistently snake_case and mostly descriptive, but the set does not follow one naming convention. It mixes noun phrases (crop_data, token_report, insider_trades) with verb phrases (lookup_company, compare_filings, verify_financial_claim), and pairs like latest_filings/recent_filings create avoidable confusion.
31 tools is too many for what is nominally an SEC Filings server, and the scope sprawls into unrelated domains such as EVM gas, tokens, prediction markets, crop data, and x402 auditing. The count does not feel earned by a coherent workflow; it feels like an uncurated bundle of endpoints.
The SEC filing workflow is reasonably covered: company lookup, search, latest/recent filings, section extraction, 8-K events, comparisons, ownership filings, and XBRL financial checks are all present. However, there is no full-filing retrieval endpoint, no deep company financial history beyond a single concept, and many non-SEC subdomains are only one-off data points, so the overall surface is still incomplete.