PennyQuery

Get SEC financials

get_sec_financials

Read-onlyIdempotent

Headline annual financials for a public company from its latest 10-K/20-F/40-F XBRL data on SEC EDGAR: revenue, net_income, operating_income, eps_diluted, total_assets, total_liabilities, stockholders_equity and cash. Each metric gives value, unit, the us-gaap concept used, period_start, period_end, fiscal_year, form, filed date and accession_number; a metric is null when the company doesn't report it under the standard us-gaap concept (common for IFRS filers and banks). Pass exactly one of ticker or cik. Returns "not_found" when EDGAR has no annual us-gaap data. Paid: $0.01 USDC per successful call on Base via x402; failed lookups are not charged.

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": "get_sec_financials"
  }
}

Input Schema

Name	Required	Description	Default
`cik`	No	SEC Central Index Key, e.g. "320193" or "0000320193"
`ticker`	No	Stock ticker, e.g. "AAPL"

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent and open-world behavior, yet the description adds substantial context: null semantics when a company doesn't report under the standard us-gaap concept (noting IFRS filers and banks), the 'not_found' outcome, and a pricing model ($0.01 USDC per successful call, failed lookups free). The cost and failure-charging rules are behavior an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the resource and scope, then return shape, then invocation rule, then edge cases and pricing. Dense but every sentence carries information an agent needs; no filler or restatement of the title.

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 takes on the burden of explaining the return shape and does so field-by-field (value, unit, us-gaap concept, period, fiscal_year, form, filed date, accession_number). Combined with null/failure semantics and pricing, nothing an agent needs to call or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds a mutual-exclusivity constraint ('Pass exactly one of ticker or cik') that the schema does not enforce — neither parameter is required and there is no oneOf. That is genuine semantics beyond the structured fields.

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 ('Headline annual financials for a public company from its latest 10-K/20-F/40-F XBRL data on SEC EDGAR') and enumerates the exact metrics returned. The scope (annual, headline, latest filing) is clear enough to distinguish it from sibling tools like get_sec_filings and sec_lookup_company.

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 concrete call conditions ('Pass exactly one of ticker or cik') and a fallback expectation ('Returns "not_found" when EDGAR has no annual us-gaap data'). It does not explicitly say when to prefer this over get_sec_filings or sec_lookup_company, so the sibling routing is left to inference.

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

All PennyQuery tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?