Skip to main content
Glama

Key figures per fiscal year or quarter from a company's SEC

sec_financials
Read-only

Key figures per fiscal year or quarter from a company's SEC XBRL filings, the numbers it tagged itself: revenue, net income, operating income, assets, liabilities, equity, cash, operating cash flow, diluted EPS and shares outstanding. Each value carries the form and filing date it came from. Ticker or CIK. Source: SEC XBRL API, public domain. Related tools on this server, for a different need: sec_events when you need to list a US company's latest 8-K filings and their items; sec_filings when you need to list recent SEC EDGAR filings for a company. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "company": "<company>"
    },
    "name": "sec_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoFiscal years (or 4 x quarters), 1-10, default 5
periodNoannual (default) or quarterly
companyYesTicker (AAPL) or CIK (320193)

Output Schema

NameRequiredDescriptionDefault
notesNo
yearsNo
periodNo
sourceNo
companyNo
periodsNo
currencyNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "company": {},
      +    "currency": {},
      +    "notes": {},
      +    "period": {},
      +    "periods": {},
      +    "source": {},
      +    "years": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the data source is SEC XBRL public-domain data, each value includes its source form and filing date, and calls cost $0.003 via x402 with failed calls not charged.

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 and metric list are front-loaded, and the alternative-tool and pricing notes are useful rather than redundant. The first sentence is dense, but the overall structure is efficient and each section serves a purpose.

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?

This is a read-only, three-parameter retrieval tool with an output schema and full schema description coverage. The description covers data source, returned fields, source metadata, alternatives, and payment behavior, leaving no material gap for correct invocation.

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 input schema already documents company, years, and period. The description reinforces that the company identifier may be a ticker or CIK and that figures can be annual or quarterly, but it adds little semantic detail 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?

The description states a specific resource (key financial figures from SEC XBRL filings) and enumerates the exact metrics returned. It also distinguishes this tool from sec_events and sec_filings, so an agent can identify its role 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 Guidelines5/5

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

It names the alternative SEC tools explicitly and explains the different need each serves: sec_events for 8-K filing lists, sec_filings for recent EDGAR filings. Combined with the opening statement of what this tool returns, the routing guidance is clear.

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