Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Balance Sheet

BalanceSheet
Read-only

Balance Sheet: Balance Sheet is a stock balance sheet API that returns the statement of financial position for a US public company by ticker - assets, liabilities and shareholders' equity - straight from SEC filings: current assets, cash, receivables, current liabilities, equity and more. Paid plans add total assets and liabilities, long-term debt, and liquidity and leverage ratios like current ratio, quick ratio and debt-to-equity. (Cost: 6 credits)

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

Input Schema

NameRequiredDescriptionDefault
yearNoFiscal year to retrieve. Defaults to latest available. History covers only the quarters captured so far; a missing period answers 404 listing the available ones.
tickerYesStock ticker symbol (e.g. AAPL, MSFT, ADBE)
quarterNoFiscal quarter to retrieve. Defaults to latest available.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false), so the bar is lower, and the description still adds real context beyond them: data comes straight from SEC filings, free tier returns only core line items while paid plans unlock total assets/liabilities, long-term debt and ratios, and each call costs 6 credits. It does not disclose caching, freshness lag, or rate limiting beyond the credit cost.

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 dense sentences that front-load the resource and then layer in field coverage, tier gating and cost with no filler beyond the opening. The only waste is the 'Balance Sheet: Balance Sheet is a stock balance sheet API' triple restatement, which could be trimmed without losing meaning.

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?

An output schema exists and annotations carry the safety profile, so the description only needs to supply domain context — which it does: US-only, SEC-sourced, ticker-keyed, tier-gated fields, and credit cost. Missing only minor operational details such as freshness or period coverage limits, which the schema partially handles via the year parameter.

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%, so both year and quarter are already documented, including the 404-with-available-periods behavior. The description confirms the ticker targets US public companies, which adds a meaningful constraint, but it adds nothing about year/quarter semantics. Baseline 3 applies when the schema does the heavy lifting.

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-and-resource: returns the statement of financial position (assets, liabilities, shareholders' equity) for a US public company by ticker, sourced from SEC filings. That resource is inherently distinct from siblings like IncomeStatement, CashFlowStatement and FinancialRatios, though no sibling is named explicitly. The opening phrase 'Balance Sheet: Balance Sheet is a stock balance sheet API' restates the name rather than adding information.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named (e.g., FinancialRatios for ratio-only needs, or SECFilings for raw filings). The agent must infer usage entirely from the tool name and the resource described. The only contextual routing hint is a plan-tier note, which is about access, not tool selection.

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

All APIVerve toolsInspect
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