Skip to main content
Glama

edgar__resolve

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

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

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 at all, the description carries the full behavioral burden and does meaningful work: it discloses the HTTP GET method, that responses are cached, that no API key is required, and — critically — the exact cost ($0.01 USDC on Base, eip155:8453) and the x402 payment mechanism. These are non-obvious invocation facts an agent would otherwise get wrong. It stops short of describing match/ambiguity handling or error responses.

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?

Front-loaded and dense: capability list first, then operational facts, then endpoint and price. Nearly every clause earns its place. The only wasted space is the capability list, which overlaps siblings and creates the ambiguity noted above rather than resolving it.

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 no-annotation, no-output-schema tool, the definition covers cost, payment, transport, and caching well. It does not cover what a response contains (single best match vs. candidate list), how ties or ambiguous names are resolved, or how the three parameters interact with the four advertised capabilities — gaps an agent would hit on the first call.

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% and all three parameters (q, forms, limit) are already documented in the schema, so the baseline is 3. The description adds no semantics for those fields — for instance, it never says whether 'forms' and 'limit' apply to the resolve path or only to the filing-search capability. The one extra detail, the params._meta["x402/payment"] field, is real value but is a payment mechanism rather than a clarification of the declared parameters.

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 a specific verb and resource ('resolve ticker/name/CIK' against SEC EDGAR), but then bundles in 'company profiles, XBRL financial facts, and full-text filing search' — capabilities that map directly onto the sibling tools edgar__company, edgar__financials, and edgar__search. An agent cannot tell from this text whether this tool supersedes those siblings or only resolves identifiers, so the scope is genuinely ambiguous.

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. The siblings edgar__company, edgar__financials, and edgar__search exist and are not mentioned or excluded, and nothing says what to do when a query matches multiple companies. The only routing-adjacent statement is 'no key needed', which is about auth, not selection.

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