Skip to main content
Glama

x420_gov_sec-edgar-company

Finds an SEC registrant by ticker, company name, or CIK and returns its EDGAR profile plus recent filings and document links.

Instructions

SEC EDGAR company lookup: Finds an SEC registrant by ticker, name or CIK and returns its EDGAR profile (SIC, state, exchanges, filer category, business address) with its most recent filings and document links, from SEC EDGAR (free, no key). Source: SEC EDGAR. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.05 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: matches[], company{cik, name, tickers, sic_description, state_of_incorporation, ...}, recent_filings[{form, filed, accession, url}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"query":"OC","filings":"1"}.

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": "x420_gov_sec-edgar-company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesticker (OC), company name fragment (Owens Corning) or CIK
filingsNorecent filings to list, 0–25 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.2/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing the paid model ($0.05 USDC on Base via x402, funded from X420_MCP_WALLET_PRIVATE_KEY, real money), which explains why readOnlyHint and idempotentHint are false — each repeated call costs money. It also spells out the return payload shape and that a signed receipt plus settlement transaction accompany the result, so the agent knows what side effects to expect.

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?

Purpose is front-loaded and the example is useful, but there is avoidable redundancy — 'from SEC EDGAR (free, no key). Source: SEC EDGAR.' says the same thing twice, and the disclaimer sentence is boilerplate. The return-shape enumeration earns its place because no output schema exists.

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

Completeness5/5

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

For a two-parameter lookup with no output schema, the definition covers inputs, expected identifiers, the returned fields, cost and settlement mechanics, and monetization constraints. There is nothing an agent needs in order to invoke this correctly that is missing.

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 two parameters are already documented. The description reinforces them via the example input ({"query":"OC","filings":"1"}) and repeats the filings range, but adds no syntax, matching, or ambiguity-resolution detail beyond the schema — the expected baseline when the schema does the work.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'SEC EDGAR company lookup: Finds an SEC registrant by ticker, name or CIK' and enumerates exactly what comes back (SIC, state, exchanges, filer category, filings, document links). No sibling tool in the list covers SEC registrants, so the agent can route unambiguously.

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?

It tells the agent what identifiers are acceptable as lookup keys (ticker, name fragment, CIK) and includes a worked example, which implies the usage context. But it never states when to prefer this over a sibling such as x420_gov_federal-register, nor any exclusions or prerequisites beyond the payment note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.