Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_sec_form_d_startup_leads

[0.010000 USDC via x402] Queries official SEC EDGAR EFTS Form D filings from the past 120 days and parses XML primary documents to return exact Decimal USD offering amounts, amounts sold, states, and executive rosters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fetch_sec_form_d_startup_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of parsed Form D filings to return (1 to 5, default 3).
queryYesKeyword or company query for SEC EDGAR Form D search (e.g., 'AI', 'robotics', 'biotech').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.010000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does well: it discloses the price (0.010000 USDC via x402), the authoritative source, that it parses XML primary documents, and that it returns exact Decimal USD amounts rather than approximations. It stops short of describing payment failure/quote behavior (left to the schema) or latency/rate characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the cost bracket first, then source, then output fields. No redundant phrasing and nothing that could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no output schema and no annotations, the description covers source, recency window, and returned data shape well enough to call correctly. Gaps are minor: no error/failure behavior, no note on what a missing payment signature yields, and no volume/latency expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the query, limit, and x402 payment signature parameters are already fully documented in the schema, including the 1-5 range and the Base/Polygon chain IDs. The description adds no parameter-specific meaning beyond restating that the search is keyword/company based, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Queries official SEC EDGAR EFTS Form D filings'), adds a scope window (past 120 days) and enumerates the returned fields (offering amounts, amounts sold, states, executive rosters). It does not, however, distinguish itself from the closest sibling such as fetch_sec_insider_and_8k, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is for sourcing startup fundraising leads from recent Form D filings, and the cost prefix signals it is a paid call. There is no explicit when-to-use/when-not guidance and no named alternative for related SEC filing data.

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.