Skip to main content
Glama

x420_gov_sec-edgar-company

Read-onlyIdempotent

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. Price: $0.005 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: matches[], company{cik, name, tickers, sic_description, state_of_incorporation, ...}, recent_filings[{form, filed, accession, url}].

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the critical caveat that the hosted tool does NOT return the deliverable and instead returns payment instructions, then spells out the 402/payment-signature retry flow. This is exactly the kind of non-obvious behavior an agent would otherwise trip over; nothing contradicts readOnlyHint=true or idempotentHint=true.

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-loads purpose before payment mechanics, which is the right order, and every section has a job. It loses a point for redundancy ('from SEC EDGAR (free, no key). Source: SEC EDGAR.') and for packing protocol-level retry instructions into what should be a selection aid.

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?

With no output schema, the description carries the return-shape burden and does so (matches[], company{cik, sic_description, ...}, recent_filings[{form, filed, accession, url}]). Combined with the payment caveat and pricing, an agent has everything needed to decide and act.

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 the baseline is 3; the schema already explains ticker/name/CIK and the 0-25 default-10 filings range. The description only loosely reinforces this via 'most recent filings and document links' and does not add format or edge-case guidance beyond the schema.

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?

States a specific verb and resource ('Finds an SEC registrant by ticker, name or CIK'), names the returned profile fields, and scopes the data source to SEC EDGAR. An agent can tell exactly what this tool retrieves without opening the schema.

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

Usage Guidelines4/5

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

Gives clear lookup contexts (ticker, name fragment, CIK) and an explicit alternative route ('run the local x420-mcp server with your own wallet key to pay automatically'). It does not state when NOT to use it, but the domain is narrow enough that ambiguity is low.

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