Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Bank and NBFC Metrics

get_lender_metrics
Read-onlyIdempotent

Bank and NBFC metrics for one stock with quarterly history and an available_from (filing) date per value: gross/net NPA (INR crore and %), CET1, AT1 and Tier 1 %, provisions, operating expenses, interest, deposits, advances / loans, borrowings, and a computed NIM (computed: true). Banks from 2022; NBFCs from 2021 (no NPA or capital ratios in their filings). quality marks doubtful values, e.g. reported_value_is_total_crar when a bank filed total CRAR as CET1. CRAR and CASA are not available. Read meta.field_notes. Pass as_of for point-in-time values. If meta.has_more, call again with cursor.

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_lender_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest period end, YYYY-MM-DD.
fromNoEarliest period end, YYYY-MM-DD.
as_ofNoOnly values filed on or before this date, YYYY-MM-DD. Default: today.
basisNoStatement basis. Default: both. Banks file asset quality and capital on standalone.
orderNoBy period end. Default: desc (latest first).
cursorNo`meta.next_cursor` from the previous call; repeat every other argument unchanged.
symbolNoREQUIRED. Stock symbol, e.g. "HDFCBANK".
tickerNoAlias for `symbol`.
metricsNoMetric names (array or comma-separated). Default: all. One of: gross_npa, net_npa, gross_npa_pct, net_npa_pct, cet1_pct, additional_tier1_pct, tier1_pct, provisions, operating_expenses, operating_profit_before_provisions, credit_cost, interest_earned, interest_expended, finance_costs, nim_pct, deposits, advances, loans, investments, borrowings, debt_securities.
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world, so safety is covered. The description adds substantial domain-specific behavior: banks from 2022, NBFCs from 2021 with no NPA or capital ratios, `quality` flags such as reported_value_is_total_crar, unavailable CRAR and CASA, and pagination via `meta.has_more`. This is strong beyond-annotation disclosure, though it does not address error handling or response shape.

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?

The purpose is front-loaded and the paragraph is dense but every sentence carries information: metric coverage, entity-type caveats, quality flags, unavailable fields, and pagination. The long metric list makes it run-on, but there is no filler or repetition.

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?

For a ten-parameter, domain-heavy tool with no output schema, the description covers the critical context: entity-type coverage windows, missing metrics, quality flag meaning, point-in-time `as_of`, and cursor pagination. It does not explain the standalone versus consolidated basis or the full return envelope, but the essential caveats an agent needs to call it correctly are present.

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 all ten parameters are already documented in the input schema. The description reinforces a few semantics — `as_of` for point-in-time values, `cursor` pagination, and computed NIM with `computed: true` — but adds little that the schema does not already convey. Baseline 3 is appropriate.

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 a specific verb and resource: retrieve Bank and NBFC metrics for one stock with quarterly history and filing dates. It enumerates the metric families covered and states the computed NIM field, so an agent knows exactly what this tool returns. It does not explicitly distinguish itself from siblings like get_financials, which keeps it from a 5.

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?

It gives operational guidance: pass `as_of` for point-in-time values, read `meta.field_notes`, and paginate with `cursor` when `meta.has_more`. However, it never states when to choose this tool over alternatives such as get_financials or get_credit_ratings, nor does it name any exclusions. Usage is implied rather than explicitly comparative.

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.