Skip to main content
Glama

fetch_balance_sheet

[Personal research only] Fetch annual and quarterly balance sheet data including assets, liabilities, shareholders' equity, and other financial position metrics.

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>"
    },
    "name": "fetch_balance_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'GOOGL') for which to retrieve annual and quarterly bala…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 does disclose that both annual and quarterly data are returned, but says nothing about how many periods come back, whether the data is free-tier limited, whether the symbol must be a US ticker, or how errors (invalid symbol) surface.

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?

A single efficient sentence that front-loads the resource and data frequency. The bracketed '[Personal research only]' tag is slightly distracting but short and does not bury the payload.

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?

The tool is simple (one required param, no output schema, no nested objects), so the description is close to sufficient for correct invocation. It still omits what the response looks like (line-item keys, currency, period counts), which matters for an agent that must consume the output.

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?

Only one parameter exists and schema description coverage is 100%, with the schema already giving examples ('AAPL', 'MSFT', 'GOOGL'). The description adds no format constraints such as exchange suffixes or case sensitivity, so the baseline 3 applies.

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 verb (fetch) and resource (balance sheet) and enumerates the contents: assets, liabilities, shareholders' equity, and other financial position metrics. That content list effectively separates it from fetch_income_statement and fetch_cash_flow without needing to name them explicitly, though no sibling is called out by name.

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 guidance on when to choose this over fetch_income_statement, fetch_cash_flow, or the aggregate financials tool, and no prerequisites, auth notes, or exclusions are given. Usage must be inferred entirely from the resource name.

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