Skip to main content
Glama

welcome

by com.thebalancedinvestorclub

get_balance_sheet

Read-onlyIdempotent

Balance sheet for a stock — assets, liabilities and equity at each period end. Mirrors what the Market Hub shows. Stocks only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker (e.g. AAPL). Financial statements are for stocks only — not ETFs or crypto.
periodsNoHow many periods to include. Defaults to 5; up to 20. If fewer exist, all available periods are returned.
frequencyNoReporting frequency. Defaults to quarterly.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds that data is at period end and mirrors Market Hub, which are helpful behavioral details beyond the schema. The 'Stocks only' note is redundant with the ticker parameter description.

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?

A single, dense sentence that conveys purpose, content, and constraints without wasted words. The most important information is front-loaded.

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

Completeness5/5

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

This is a simple read-only data fetch with all parameters documented and safety annotations provided. The description sufficiently covers what the tool does, including data scope and UI mirroring, so no further context is needed.

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?

All three parameters (ticker, periods, frequency) have detailed descriptions in the schema (100% coverage), so the description does not need to elaborate. It adds no additional parameter-level meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a balance sheet (assets, liabilities, equity) for a stock at period-end. This distinguishes it from sibling tools like get_income_statement and get_cash_flow, and the 'Stocks only' constraint is explicit.

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?

The description implies when to use this tool (for stock balance sheet data) and notes it mirrors Market Hub, providing useful context. It does not explicitly name alternative tools, but the 'Stocks only' exclusion is clear.

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

All welcome toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

With 57 tools, most have distinct purposes (market data, journaling, watchlists). A few related tools (get_price_alignment vs get_crypto_price_alignment, get_market_pulse vs get_market_movers) could cause miselection, but descriptions clarify asset types and scope.

Naming Consistency4/5

Tools predominantly use get_/list_/create_/update_/delete_ verbs with clear noun suffixes. Minor deviations like start_here, whoami, add_to_watchlist, and remove_from_watchlist break the pure verb_noun pattern, but the style is consistent and readable.

Tool Count1/5

At 57 tools, the server is far beyond the well-scoped range. While the domain is broad, this many tools will overwhelm an agent's capability to select accurately, and many could be consolidated (e.g., separate financial statements).

Completeness5/5

The server covers watchlist CRUD, trading journaling, market data (fundamentals, statements, news, transcripts), analysis tools, and community features. No obvious dead ends; lifecycle coverage is thorough for the described domain.

Resources