Skip to main content
Glama

sec_financials

Fetch SEC EDGAR XBRL financial facts by ticker or CIK—revenue, net income, assets, cash flow, debt, shares, and recent 10-K/10-Q/8-K filings for 1–5 fiscal years plus the current quarter.

Instructions

US public company financial facts from SEC EDGAR XBRL (by ticker or CIK): revenue, net income, operating income, gross profit, diluted EPS, assets, liabilities, equity, cash, operating cash flow, long-term debt, shares outstanding — last 1-5 fiscal years plus latest quarter, with form, filing date and accession; plus recent 10-K/10-Q/8-K filings. Any raw us-gaap tag also accepted. Costs 0.005 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK (alternative)
yearsNo1-5, default 3
tickerNoTicker, e.g. AAPL
metricsNoComma list: revenue,net_income,… or us-gaap:Tag

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.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 full burden and does substantial work: it discloses the per-call cost (0.005 USDC on Base, x402), that charges apply per successful call, and that a caller without a payment key receives a 402 challenge rather than data. It also states the temporal coverage limits and the return fields (form, filing date, accession). It stops short of describing rate limits or failure modes beyond the 402 case.

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?

The purpose, coverage and metric list are front-loaded, and the payment caveat is placed last where it belongs. The single dense paragraph is efficient overall, though the long metric enumeration could have been trimmed since the metrics parameter already lists options.

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 four-parameter, zero-required read tool with no output schema, the definition covers what is returned, the time range, and the payment/authentication gate. The remaining gap is the absence of any note on error behavior beyond the 402 challenge or on how multiple metrics are returned together.

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 all four parameters are already documented in the schema, which sets the baseline at 3. The description reinforces that lookup can be by ticker or CIK and that arbitrary 'us-gaap' tags are accepted, but that capability is already present in the metrics schema field, so little new meaning is added.

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 precise verb-and-resource statement: 'US public company financial facts from SEC EDGAR XBRL (by ticker or CIK)'. It then enumerates the concrete metrics returned and the coverage window (last 1-5 fiscal years plus latest quarter), plus the recent filings add-on, so an agent knows exactly what data this tool yields.

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 context is implied by the scope (US SEC-registered companies, identified by ticker or CIK), and the payment precondition is stated explicitly. However, there is no guidance on when to prefer this over a generic lookup or filings-oriented sibling, and no exclusions (e.g. non-US issuers, non-XBRL data) are called out.

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