Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

sec_company_financials

Fetch live SEC EDGAR submissions and ASC 606 XBRL facts by ticker/CIK to separate 10-K annual and 10-Q quarterly revenue, net/operating income, cash flow, assets, cash, and shares; no API key needed.

Instructions

Fetch live official SEC EDGAR submissions and ASC 606 XBRL companyfacts for a public company by ticker or CIK, separating annual 10-K vs quarterly 10-Q revenue, net income, operating income, cash flow, assets, cash, and shares. Zero API key required.

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": {
      "ticker_or_cik": "<ticker_or_cik>"
    },
    "name": "sec_company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_emailNoOptional contact email included in the SEC Fair Access User-Agent header.
ticker_or_cikYesStock ticker symbol (e.g. 'AAPL', 'NVDA') or numeric SEC CIK (e.g. '0000320193').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 burden well: it declares the authoritative source ('live official SEC EDGAR'), states no API key is needed, and the schema-linked contact_email is tied to SEC Fair Access User-Agent behavior. It stops short of disclosing rate-limit handling, failure behavior for unknown tickers, or caching/freshness, which keeps it below 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?

A single front-loaded sentence that opens with the verb and source before the metric list, with no filler. It is dense but readable; the enumerated field list is the only element that slightly weighs it down.

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?

There is no output schema, so the description must convey the return content, and it does by naming the metric set and the annual-vs-quarterly separation. It leaves response shape, units/currency, and number of periods unspecified, which is a modest gap for a data-retrieval tool.

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 both parameters are already fully documented in the schema, including accepted ticker and CIK formats and the User-Agent role of contact_email. The description adds no per-parameter semantics beyond that, so the baseline 3 applies.

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?

Uses a specific verb ('Fetch') against a specific resource ('SEC EDGAR submissions and ASC 606 XBRL companyfacts') scoped by ticker or CIK. It enumerates the metrics returned (revenue, net income, operating income, cash flow, assets, cash, shares) and the 10-K vs 10-Q split, so an agent can tell it apart from the sibling sec_form_d_funding_search 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 Guidelines3/5

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

Usage is only implied: 'public company by ticker or CIK' plus 'Zero API key required' tells the agent this is a free read for public-company fundamentals. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. Form D funding data) for cases this tool does not cover.

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