Agent Tools

sec_facts

Financial figures over time from SEC XBRL filings for a US-listed company by ticker or CIK: revenue, net income, EPS, assets, liabilities, cash, operating income, equity, shares, or any us-gaap tag. Annual or quarterly series with period dates, fiscal year, form, filing date and accession number, latest filing per period. Pairs with sec_filings. Raw public data, not investment advice. Price $0.01 USDC per call via x402. Example output: {"company":{"name":"Apple Inc.","cik":"320193"},"concept":{"tag":"NetIncomeLoss","label":"Net Income (Loss) Attributable to Parent","unit":"USD"},"period":"annual","returned":1,"values":[{"start":"2024-09-29","end":"2025-09-27","value":112010000000,"fiscal_year":2025,"fiscal_period":"FY","form":"10-

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

Input Schema

Name	Required	Description
`cik`	No	Optional SEC CIK, e.g. 320193
`limit`	No	1 to 40, default 10
`period`	No
`ticker`	No	Stock ticker, e.g. AAPL. Give ticker or cik
`concept`	No	revenue (default), net_income, eps, assets, liabilities, cash, operating_income, equity, shares, or a us-gaap tag

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the payment requirement ($0.01 USDC per call via x402), the data provenance (raw public SEC data, not investment advice), and the de-duplication rule ('latest filing per period'). It does not cover error cases or rate limits, but the key operational facts are present.

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 information-dense, with no filler sentences. However, the trailing 'Example output' block is truncated mid-string, which is sloppy and reduces the value of the space it consumes.

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?

There is no output schema, so the inline example output is genuinely useful in showing the returned shape (company, concept, period, values with dates and form). Combined with the pricing and provenance notes, an agent has enough to call it correctly, though the truncated example weakens it slightly.

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 coverage is 80%, so the schema already documents most parameters; the description mostly restates the concept list and the ticker/CIK option. It adds a little beyond the schema by describing the annual/quarterly series shape, but `limit` and default semantics come from the schema alone.

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 resource (SEC XBRL financial figures) with the supported concepts enumerated and the lookup key (ticker or CIK). It distinguishes itself from the sibling sec_filings by framing itself as the numeric-facts companion.

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?

'Pairs with sec_filings' hints at the split between facts and filing documents, and 'Give ticker or cik' implies the lookup requirement, but there is no explicit when-to-use/when-not statement naming alternatives. Usage is implied rather than spelled out.

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

All Agent Tools 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?