Skip to main content
Glama

Kempt Horizon Data Toolkit

SEC key financials

sec_company_financials
Read-only

Revenue, net income, EPS, assets, cash and more from XBRL filings, annual or quarterly.

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_company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK, e.g. 320193
limitNo
periodNoannual
tickerNoStock ticker, e.g. AAPL
metricsNoSubset of: revenue, netIncome, operatingIncome, grossProfit, epsDiluted, epsBasic, totalAssets, totalLiabilities, stockholdersEquity, cash, operatingCashFlow, sharesOutstanding

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 provenance (values come from XBRL filings) and scoping (annual vs quarterly), but omits behaviorally relevant facts: what happens when neither cik nor ticker is supplied, whether values are normalized to USD, and how many periods are returned.

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 leads with the returned content rather than the tool name. No filler, though 'and more' is a mild waste of tokens that could have named the remaining metrics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no output schema, and an open-world data source, the description should clarify the return shape (e.g., a series of periods with units) and which identifier to supply. It conveys the metric and period dimensions but leaves identifier selection and response structure to inference.

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

Parameters2/5

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

Schema coverage is only 60% and the description compensates minimally: 'Revenue, net income, EPS, assets, cash' echoes the metrics enum already listed in the schema, and 'annual or quarterly' just restates the period enum. The limit parameter is undocumented in both places, and nothing explains the cik/ticker relationship or that metrics accepts a comma string or array.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource concretely (revenue, net income, EPS, assets, cash) and the data source (XBRL filings) plus the period dimension, so an agent knows it retrieves reported financial metrics rather than filing documents. It does not explicitly distinguish itself from the sibling sec_company_filings or sec_company_profile, so the boundary is inferred rather than stated.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus sec_company_filings, sec_company_profile, or sec_filing_search, nor does it state prerequisites such as needing a CIK or ticker. The phrase 'annual or quarterly' hints at the period choice but is not framed as usage guidance.

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