Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Batch Financial Statements

get_batch_financials
Read-onlyIdempotent

One financial statement section for up to 10 companies in one call, for comparing them: the same numbers and available_from dates as get_financials, latest periods per company. Results are in input order, one per symbol; a symbol that fails gets found:false and the reason. Charged as one call per company found.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_batch_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsNoLatest N periods per company (default 6, max 12).
sectionNoquarterly (default), profit_loss, balance_sheet, cash_flow or ratios.
symbolsNoREQUIRED. Up to 10 stock symbols, e.g. ["TCS","INFY"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious traits on top: results are returned in input order, one entry per symbol, partial failures surface as found:false plus a reason, and billing is one call per company actually found. The cost/quota model and partial-failure semantics are exactly the kind of behavior an agent cannot derive from annotations or schema.

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?

Three tight sentences that front-load scope, then equivalence, then result/error/billing semantics. Dense and economical, no filler or repeated information.

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?

For a batch read tool with no output schema, the description covers the shape of the return (one per symbol, ordered by input, found:false with reason on failure) and points to get_financials for the field-level payload. Nothing an agent needs in order to call it correctly 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 100%, so periods, section and symbols are already documented in the schema, and the description largely restates them ('latest `periods` per company'). It adds no new syntax, default, or constraint information beyond what the schema provides, so the baseline 3 applies.

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?

States a specific resource (one financial statement section), an explicit scope limit (up to 10 companies in one call), and names the single-company sibling get_financials with the equivalence claim 'the same numbers and available_from dates'. An agent can immediately tell this apart from get_financials without inspecting either schema.

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?

'for comparing them' gives the intended use case, and the explicit reference to get_financials implies the single-company alternative. It never states an explicit exclusion (e.g. 'use get_financials if you only need one symbol'), so the routing guidance is clear but not fully spelled out.

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.