Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Company financials: income statement, balance sheet, cash flow

sec_financials
Read-only

Company financial statements for a US-listed company by ticker or CIK, from its SEC 10-K and 10-Q filings (XBRL): revenue, gross profit, operating and net income, EPS, cash, assets, debt, equity, operating cash flow, capex, free cash flow, dividends and buybacks, with margins, growth, ROE and current ratio. Annual or quarterly, up to 10 periods. Use for fundamentals, a valuation or a company comparison. Example: ticker=AAPL. Price $0.02/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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 Central Index Key, e.g. 320193 (instead of ticker)
limitNoPeriods to return, newest first: 1-10 (default 4)
periodNoannual (default) or quarterly
tickerNoStock ticker or company name, e.g. AAPL (or give cik)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with "reads or computes only and changes nothing". Beyond that it adds material context the annotations cannot convey: cost ($0.02/call via x402 USDC or card key), a 25-call free tier, failed calls being free, and the warning that each repeat call is charged. That pricing/side-effect disclosure is exactly the kind of behavior an agent needs before retrying.

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-loaded with the core identity, then coverage, then usage, then pricing and safety. The long field enumeration is dense but earns its place by telling the agent what data is actually available without an output schema. No filler sentences.

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?

There is no output schema, so the description must convey return content, and it does thoroughly: income statement, balance sheet, cash flow items plus derived margins, growth, ROE and current ratio, with period granularity. Combined with explicit cost and read-only behavior, an agent has everything needed to call it correctly and decide whether to retry.

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 ticker, cik, limit and period are already documented in the input schema with examples and defaults. The description restates the annual/quarterly choice, the up-to-10-period bound, and the ticker=AAPL example, adding light reinforcement rather than new semantics. Baseline 3 is appropriate when the schema carries the detail.

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?

States a precise verb-and-resource combination: financial statements for a US-listed company by ticker or CIK, sourced from SEC 10-K/10-Q XBRL data, and enumerates the specific line items and derived metrics returned. The scope (annual vs quarterly, up to 10 periods) is explicit. It does not explicitly contrast itself with the sibling income_statement tool, which is the only thing keeping it from a 5.

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?

"Use for fundamentals, a valuation or a company comparison" gives concrete task contexts that map to real agent intents, and the ticker=AAPL example anchors the call. There is no explicit when-not guidance or named alternative for narrower needs (e.g. a single statement), so it stops short of full routing 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.