Crypto, web, finance and app data tools

Company Financial Health Report

company_financial_health_report

Financial health report of any US-listed company from its SEC filings, by ticker or name: 0-100 health score with reasons, verdict, latest annual figures, 5-year revenue and profit CAGR, margin and free cash flow trend, insider open-market buys and sales, and recent 10-K, 10-Q and 8-K links. Use for stock research, credit checks or a quick read on a public company.

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": {
      "company": "<company>"
    },
    "name": "company_financial_health_report"
  }
}

Input Schema

Name	Required	Description	Default
`company`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the report is built from SEC filings and scoped to US-listed companies and previews the returned components, but it does not state read-only safety, rate limits, data freshness, error behavior, or coverage limitations beyond US listing.

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?

The description is front-loaded with the tool's scope and output summary, followed by concise use cases. The output list is dense but each element is relevant to the report's value proposition, so it is appropriately sized for a complex composite tool.

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?

Given one required parameter, no annotations, and an existing output schema, the description supplies enough context about input flexibility, data source, scope, and report contents. It leaves minor gaps around methodology limitations and alternatives, but the core information needed to invoke the tool is present.

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 description coverage is 0%, so the description usefully clarifies that the sole company parameter accepts either a ticker or a company name. It does not provide examples or exact formatting, but it compensates adequately for the otherwise undocumented parameter.

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 states a specific aggregate resource: a financial health report for US-listed companies sourced from SEC filings, with health score, verdict, fundamentals, trends, insider activity, and filing links. It is clear what the tool produces, though it does not explicitly compare itself to nearby siblings such as us_company_fundamentals, us_company_filings, or insider_trades.

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 clear usage contexts: stock research, credit checks, and a quick read on a public company. It does not state when not to use it or name alternative tools for raw fundamentals, filings, or insider trades, so it falls short of explicit alternative guidance.

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?