Skip to main content
Glama
Sign In

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Company financials from SEC filings

sec_financials
Read-only

Get a US public company's financials as filed with the SEC: revenue, operating income, net income, diluted EPS, total assets, liabilities, equity, cash, operating cash flow and shares outstanding — last 4 fiscal years plus the latest quarter, each tied to its filing.

$0.004 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need a US public company's reported numbers. Use instead: company_snapshot to get the profile and filings in the same call; company_due_diligence for computed ratios. Parameters: ticker or cik (one is required). Returns: revenue, operating and net income, diluted EPS, assets, liabilities, equity, cash, operating cash flow and shares, for the last 4 fiscal years and the latest quarter, each tied to its filing.

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. Give this or ticker.
tickerNoUS stock ticker, e.g. "NVDA". Give this or cik.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key. Give this or ticker."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new behavioral context: a $0.004 USDC x402 price, that failed calls are free, and a two-step quote-then-sign payment flow via the optional `payment` parameter. It does not cover latency or data freshness, so not a full 5.

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

Conciseness3/5

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

Front-loaded and well-sectioned with When/Use/Parameters/Returns headers, but the Returns section repeats the opening field list almost verbatim (revenue, operating and net income, diluted EPS, assets, liabilities, equity, cash, operating cash flow, shares), which is wasted space.

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 carries the return-shape burden and does so, listing the fields and their coverage window (4 fiscal years plus latest quarter, each tied to its filing). The payment mechanic is also explained end to end.

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 schema documents cik, ticker and payment, making 3 the baseline. The description earns above baseline by stating 'ticker or cik (one is required)' — a constraint the schema does not enforce, since the required array is empty — and by hinting at the quote flow for `payment`.

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 first sentence names a specific verb (Get) and resource (US public company financials as filed with the SEC) and enumerates the exact line items returned, so an agent knows precisely what it gets. It also distinguishes itself from siblings by naming company_snapshot and company_due_diligence as different scopes.

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?

Explicit 'When to use' plus a 'Use instead' clause that names two alternative tools and the condition under which each is preferable. Nothing about 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 Tollkit toolsInspect
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