Crypto, web, finance and app data tools

us_company_fundamentals

Reported financials of a US-listed company from SEC 10-K/10-Q filings by ticker: revenue, profit, EPS, cash flow, free cash flow, assets, debt, equity and margins, annual or quarterly. Use when analysing or comparing US stocks and you need filed numbers, not estimates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "us_company_fundamentals"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`period`	No	annual
`ticker`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the data source, that values are as-filed rather than estimated, and that both annual and quarterly periods are available, but it says nothing about history depth, data freshness/lag, auth or rate limits, or how an invalid ticker is handled.

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?

Two sentences, front-loaded with the resource and source before the usage cue. The metric list is long but earns its place by previewing the returned fields; there is no filler or repetition.

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?

For a simple three-parameter read tool with an output schema, the definition covers what the tool returns, its source, and its periodicity, so the agent need not have return values explained. The remaining gap is the undocumented limit parameter and the unaddressed overlap with us_company_filings.

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 0%, so the description must compensate. It adds meaning for ticker ('US-listed company... by ticker') and period ('annual or quarterly'), but the limit parameter is never mentioned and the period values are not given as explicit options, leaving one of three parameters fully undocumented.

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 specific resource (reported financials of a US-listed company), the source (SEC 10-K/10-Q filings), the lookup key (ticker), and enumerates the reported metrics and periodicity. It does not differentiate itself from the sibling us_company_filings, which shares the filing-based domain, so it falls short of 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?

It gives a clear use context ('analysing or comparing US stocks and you need filed numbers') and an implicit exclusion via 'not estimates', which meaningfully narrows the tool's role. It stops short of naming an alternative tool or stating when not to use it, so no explicit sibling routing.

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

All Crypto, web, finance and app data 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?