Skip to main content
Glama

edgar__company

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/company

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__company"
  }
}

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.1/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 meaningfully discharge it: it discloses that responses are cached, that the call is a read-only HTTP GET, that no API key is required, and precisely how payment works ($0.01 per call in USDC on Base eip155:8453 via x402 in params._meta["x402/payment"]). This is well beyond schema-level information. It falls short of a 5 because rate limiting is only characterized as 'polite' and nothing is said about failure modes such as unpaid calls, unknown tickers, or empty results.

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

Conciseness4/5

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

The description is front-loaded with what the tool provides and keeps the payment and endpoint details compact in short clauses. The payment/endpoint boilerplate consumes roughly a third of the text and is generic across the API rather than tool-specific, but no sentence is purely redundant.

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 3-parameter tool with no output schema and no annotations, the description covers the essential mechanics: endpoint, auth/payment, caching, and capability list. It is incomplete on the points that matter most for correct invocation, namely which capability a given q/forms/limit combination triggers and what a response contains.

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 schema already documents q, forms, and limit, making 3 the baseline. The description adds only marginal meaning, implicitly connecting 'resolve ticker/name/CIK' and 'full-text filing search' to the q parameter. It says nothing about how forms or limit interact with the different capability modes, nor about which q forms are accepted for which mode.

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 does name the resource (SEC EDGAR company data) and enumerates capabilities: ticker/name/CIK resolution, company profiles, XBRL financial facts, and full-text filing search. However, it bundles four distinct functions into one tool and never distinguishes this from siblings such as edgar__resolve, edgar__financials, and edgar__search, which appear to cover exactly those capabilities. The multi-capability framing leaves the agent unsure what this specific tool uniquely returns.

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 is provided, and no alternative is named despite obvious overlap with edgar__resolve, edgar__financials, and edgar__search. The notes about caching and no key being needed are operational facts rather than selection guidance.

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