Skip to main content
Glama

Valeur Intrinsèque

get_financial_statements

Last five reported years of one financial statement: income, balance, or cashflow. Not counted in the Score VI quota.

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": {
      "symbol": "<symbol>",
      "statement": "<statement>"
    },
    "name": "get_financial_statements"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker or company name (e.g. AAPL, LVMH)
statementYesStatement type: income (income statement), balance (balance sheet), or cashflow (cash flow statement)

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 disclosure burden, and it does deliver two real behavioral facts: results are capped at five reported years and requests are scoped to one statement type at a time. However, it reveals nothing about return shape, units/currency normalization, restatements, or whether data is consolidated vs. parent-only — meaningful gaps for a data-retrieval tool.

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 short sentences, no padding, with the core scope statement front-loaded. The trailing quota note is terse and uses unexplained internal terminology ('Score VI quota'), which costs a point on clarity rather than brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool this covers the essentials, and both parameters are fully documented in the schema. Since there is no output schema and no annotations, the description should say more about what a response contains (line items, units, ordering) than it currently does.

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 100%, with the statement enum fully documented in the schema itself, so the baseline is 3. The description restates the same three statement values and adds only a scope hint (five years) that is not parameter-specific.

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 names the resource (a financial statement), the scope (last five reported years), and the three variants (income, balance, cashflow), which is enough for an agent to tell this raw-history tool apart from the metrics/valuation siblings. It never explicitly contrasts itself with a sibling, which keeps it out of 5 territory.

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?

Usage is only implied: because it returns five years of a single raw statement, an agent can infer it is for historical statement retrieval rather than for derived scores. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the valuation and scoring siblings.

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