Skip to main content
Glama

edgar__financials

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

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

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.4/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 a solid job: it discloses caching, rate-limit politeness, that no API key is required, a concrete cost ($0.01/call in USDC on Base), the payment channel (x402 via params._meta["x402/payment"]), and the exact HTTP method and URL. What it omits is any sense of return shape or failure behavior (e.g., what happens on an unpaid call), which keeps it short of a 5.

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?

Two dense sentences that front-load the capability list and then the operational facts (cost, payment, endpoint); nothing is padding. The capability enumeration is a bit of a grab-bag and could be structured as modes, but no sentence is wasted.

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 paid, keyless HTTP gateway tool with no output schema and no annotations, the description covers the details that most affect correct invocation: price, currency, chain, payment location, and endpoint. It falls short on explaining how the four advertised capabilities relate to the three parameters and what a response contains, but that gap is moderate rather than disqualifying.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not contain: it documents a fourth, undeclared input path (params._meta["x402/payment"]) that the caller must populate for the call to succeed. It still doesn't clarify that `forms` presumably only applies to the filing-search mode, so the added value is real but partial.

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 names concrete resources (ticker/CIK resolution, company profiles, XBRL facts, filing full-text search), but it bundles four distinct capabilities into one tool without saying which one this endpoint actually performs by default or how `q` selects among them. Given siblings named edgar__resolve, edgar__company, and edgar__search, an agent cannot tell from this text why it should pick edgar__financials instead of one of those.

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?

There is no when-to-use or when-not-to-use guidance and no reference to any alternative tool. The only conditional information is about payment and transport, not about task selection, so an agent must infer the selection rule from the capability list alone.

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