Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_risk_metrics

Calculate Sharpe, Sortino, max drawdown, and volatility versus a benchmark for an Indian stock as of a chosen date, using a configurable lookback window.

Instructions

Sharpe, Sortino, max drawdown, volatility vs benchmark.

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

Input Schema

NameRequiredDescriptionDefault
as_ofNo
symbolYes
benchmarkNo^NSEI
lookback_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing: no data source, no computation window caveats, no rate limits, no indication that the default benchmark is an Indian index (^NSEI) and what that implies for non-Indian symbols. The only behavioral signal is that volatility is measured relative to a benchmark.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but this is under-specification rather than conciseness: a single fragment with no main verb and no lead-in stating what the tool does. Nothing is front-loaded because there is no sentence structure to front-load.

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

Completeness2/5

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

An output schema exists, so return-value explanation is not required, but for a four-parameter analytics tool with no annotations this description leaves the agent unable to call it confidently. The essential facts — what a symbol means here, what the lookback window controls, and how the benchmark default affects results — are absent.

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

Parameters2/5

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

All four parameters have 0% schema description coverage, so the description must compensate and largely does not. The phrase 'vs benchmark' hints at the benchmark parameter, but symbol, as_of, and lookback_days (default 252) are entirely unexplained, including what format as_of accepts or how lookback_days interacts with the benchmark comparison.

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

Purpose3/5

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

The description names the concrete metrics returned (Sharpe, Sortino, max drawdown, volatility vs benchmark), which tells an agent what the tool produces. However, it is a bare noun phrase with no verb and no statement of scope (per-symbol? per-portfolio?), and it offers no differentiation from siblings like get_returns or get_peer_comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no when-not-to-use, and no named alternative. An agent cannot tell from this text whether to call get_risk_metrics or get_returns first, or what circumstances favor one over the other.

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