Skip to main content
Glama

Companies Daily – SEC filings of US companies

XBRL totals of a company

get_financials
Read-onlyIdempotent

Revenue, net income, total assets, total liabilities, stockholders’ equity and cash from the XBRL data a company filed with the SEC, by calendar-year frame (up to 3 years), in US dollars.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK, leading zeros optional, e.g. "320193".
tickerNoTicker symbol, e.g. "AAPL" (used when cik is empty).

Output Schema

NameRequiredDescriptionDefault
urlYes
as_ofNo
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the numbers come from SEC XBRL filings, cover up to 3 calendar-year frames, and are denominated in US dollars. It does not state what happens when a company has no XBRL data or how sparse filings are handled.

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?

One dense sentence with zero filler. The most decision-relevant information, the list of returned metrics, is front-loaded, followed by source, window, and currency. Nothing repeats the annotations or the schema.

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?

With an output schema present, the description needn't explain return shape, and for a two-parameter read tool it covers source, scope, and units well. The one gap is that neither parameter is required, yet the description never states that at least one of cik or ticker must be supplied, nor what an empty call does.

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%, and the schema already explains the CIK pattern and that ticker is used when cik is empty. The description adds nothing about the cik/ticker tradeoff or precedence. Baseline 3 is appropriate since the schema carries the parameter semantics.

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?

The description names the exact line items returned (revenue, net income, total assets, total liabilities, stockholders' equity, cash from operations), the data source (XBRL data filed with the SEC), and the framing window (calendar-year, up to 3 years). That is far more specific than the title 'XBRL totals of a company'. It does not explicitly contrast itself with siblings such as get_company, so it lands at 4 rather than 5.

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 implied by the content: an agent can infer this is the tool for pulling historical headline financials for a company. There is no explicit statement of when to prefer it over get_company, no prerequisite notes, and no exclusions. Adequate but the routing decision 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources