finstack-mcp

bse_quote

Retrieve real-time BSE stock quotes for Indian equities, including current price, change, volume, market cap, and key ratios.

Instructions

Get real-time BSE (Bombay Stock Exchange) quote for an Indian stock.

Returns current price, change, volume, market cap, and key ratios.

Args: symbol: BSE stock symbol (e.g., RELIANCE, TCS, INFY)

Examples: bse_quote("RELIANCE") → Reliance Industries BSE price bse_quote("TCS") → TCS BSE price

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

Input Schema

Name	Required	Description	Default
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Mar 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the real-time nature and the return fields (price, change, volume, market cap, key ratios). It does not mention limitations such as rate limits or invalid symbol handling, but the provided details go beyond a bare 'get quote' statement.

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?

The description is concise: a purpose sentence, a return-field sentence, one parameter definition, and two examples. It is front-loaded with the core purpose and contains no unnecessary verbiage.

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 simple one-parameter quote tool, the description covers purpose, return content, parameter semantics, and usage examples. Since an output schema is present (as per context), it need not describe the full return structure. The description is complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no description for the 'symbol' parameter (0% coverage). The description compensates by defining it as a 'BSE stock symbol' and providing concrete examples (RELIANCE, TCS, INFY) plus usage examples that clarify the expected input format.

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 it 'Get real-time BSE (Bombay Stock Exchange) quote for an Indian stock' and lists return fields (current price, change, volume, market cap, key ratios). This specific verb+resource distinguishes it from siblings like nse_quote and live_quote.

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?

Usage is implied via the BSE focus and examples, but there is no explicit guidance on when to use this tool over alternatives (e.g., nse_quote) or when not to use it. The description does not state exclusions or direct comparisons.

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

Deploy Server