Skip to main content
Glama

falcon.sol comps

get_financials

falcon.sol: Standardized financials (up to 15 FY + TTM, balance sheet, ratios, XBRL provenance) from SEC EDGAR. Costs $0.015 USDC (x402).

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": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNo
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 burden and does disclose two important behaviors: the data source (SEC EDGAR) and that invocation costs $0.015 USDC via x402, which tells the agent this is a paid call. It omits error behavior, coverage limits for non-US tickers, and any latency/rate-limit context.

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?

Two tight sentences, front-loaded with what the tool returns, followed by source and price. Nothing is padded or redundant.

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 2-parameter read tool with no output schema and no annotations, the description covers what data comes back, where it comes from, and the payment requirement. Gaps remain around output granularity (currency/units), behavior on unknown tickers, and the preview-vs-full distinction, but nothing essential to making the call is missing.

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 partially does: 'up to 15 FY + TTM' explains the semantics and cap of the `years` parameter, and 'from SEC EDGAR' implies `ticker` is a US listing symbol. It does not clarify defaults, whether TTM is always returned alongside the requested years, or how non-US/non-filer tickers behave.

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?

Names a specific resource (standardized financials from SEC EDGAR) and enumerates the payload (balance sheet, ratios, XBRL provenance, up to 15 FY + TTM). It does not explicitly differentiate itself from siblings such as preview_financials or get_comps, so the agent must infer when this fuller version is preferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no reference to the clearly related siblings (preview_financials, get_comps, get_credit). The mention of price is useful context but is not usage 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.

Resources