Skip to main content
Glama
mcp-india-stack

mcp-india-stack

get_stock_quote

Read-onlyIdempotent

Fetch the current delayed price and summary for an Indian stock ticker to support quick market checks.

Instructions

[Experimental] Fetch current (delayed) price and summary for a given Indian stock ticker.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock symbol/ticker to fetch. Examples: RELIANCE.NS, INFY.NS, TCS.BO

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description contributes non-obvious behavior the annotations cannot convey: that the data is delayed rather than real-time, that the tool is experimental, and that it is limited to Indian equities — all material to how an agent should present the result.

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 sentence with the experimental caveat front-loaded and the latency caveat parenthetical, so the two most decision-relevant facts arrive first. Nothing is redundant or padded.

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?

With an output schema present, return-value detail is already handled, and the one required parameter is fully documented in the schema. The description covers the two things structured fields cannot: experimental status and delayed pricing. Error behavior for malformed or non-Indian tickers is the only notable omission.

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 coverage is 100% and the symbol parameter already carries exchange-suffixed examples (RELIANCE.NS, INFY.NS, TCS.BO). The description adds only the 'Indian stock ticker' constraint, which is genuinely useful scoping but marginal beyond what the schema provides.

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 gives a specific verb ('Fetch') and resource ('current price and summary') scoped to 'Indian stock ticker', which implicitly separates it from get_stock_history (past) and from the validator/calculator siblings. It stops short of naming get_stock_history outright, so the differentiation is inferred rather than stated.

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?

The word 'current' plus the sibling list implies this is the endpoint for live-ish quotes rather than historical series, but the description never says so explicitly or names get_stock_history as the alternative. No preconditions or exclusions are given, leaving the agent to infer usage from the name.

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

Deploy Server

Other Tools