Skip to main content
Glama

edgar__search

SEC EDGAR data as a GET API: resolve ticker/name/CIK, company profiles, XBRL financial facts, and full-text filing search. Cached, polite, no key needed. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/edgar/search

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": {
      "q": "<q>"
    },
    "name": "edgar__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesticker, company name or CIK
formsNofiling form filter, e.g. 10-K
limitNomax results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / forms
      Added value: +{
      +  "description": "filing form filter, e.g. 10-K",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (1-100)"New value: +"max results"
    • removedInput schema / properties / period
      Removed value: -{
      -  "description": "all, annual or quarterly",
      -  "enum": [
      -    "all",
      -    "annual",
      -    "quarterly"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / q / description
      Previous value: -"Ticker, company name or CIK, e.g. AAPL, nvidia, 320193"New value: +"ticker, company name or CIK"
    • removedInput schema / properties / tag
      Removed value: -{
      -  "description": "XBRL tag or alias: revenue, net_income, assets, cash, eps, or any us-gaap tag",
      -  "type": "string"
      -}
  2. First observed

TDQS

B3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it does disclose meaningful operational facts the schema cannot: response caching, no API key required, and a per-call price of $0.01 in USDC on Base settled via x402 in params._meta['x402/payment']. It does not say what happens when payment is absent or invalid, nor what errors/latency to expect — 'polite' is asserted but unquantified.

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

Conciseness3/5

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

Compact and reasonably front-loaded, with payment and transport details at the end. But the opening sentence spends words on capabilities this endpoint may not expose, which dilutes focus rather than earning its place.

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

Completeness3/5

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

For a three-parameter, no-output-schema search tool the payment and caching disclosures are the important additions and they are present. Missing is the relationship to sibling EDGAR tools and any sense of result shape or pagination behavior via the 'limit' parameter.

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 coverage is 100%, so q, forms and limit are already documented in the schema; the description only obliquely reinforces that q is a ticker/name/CIK and that forms is a filing filter. Baseline 3 applies since the schema does the heavy lifting.

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

Purpose3/5

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

The description enumerates the whole EDGAR service surface (ticker/CIK resolve, company profiles, XBRL facts, full-text filing search) rather than stating what this specific 'search' endpoint does. The final URL path hints at full-text filing search, and the params (q, forms, limit) are search-shaped, but an agent cannot tell from the text which of the four listed capabilities belongs to this tool versus siblings like edgar__company, edgar__financials or edgar__resolve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, and no routing cues toward the sibling EDGAR tools even though the description itself names capabilities those siblings presumably implement. The only implicit signal is the HTTP path '/edgar/search'.

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.

Resources