Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_returns

Compute simple or log returns for Indian stocks over chosen lookback windows as of a specified date for point-in-time analysis.

Instructions

Simple/log returns over lookback windows, computed in pandas.

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

Input Schema

NameRequiredDescriptionDefault
as_ofNo
symbolYes
windowsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions that computation happens in pandas, which is an implementation detail rather than useful behavioral context, and says nothing about permissions, data sources, handling of missing data, frequency assumptions, or side effects beyond the implied read-only 'get'.

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

Conciseness3/5

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

The description is a single short sentence with no wasted framing, but it is under-specified for a three-parameter financial tool. The slash construction 'Simple/log' is awkward and reduces clarity rather than saving space.

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?

Although an output schema exists and covers return values, the description is incomplete relative to the tool's complexity. With no annotations and 0% schema parameter coverage, the agent lacks essential context about how the tool computes returns, what the windows mean, and how as_of affects results.

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?

Schema description coverage is 0%, so the description must compensate. It only loosely hints at the 'windows' parameter via 'lookback windows'; it gives no meaning for 'as_of' or 'symbol' and does not clarify valid window values, defaults, or how simple versus log returns are selected.

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 resource (returns) and the computation scope (over lookback windows), but the phrase 'Simple/log returns' is ambiguous: it is unclear whether the tool returns simple returns, log returns, or supports both. It does not distinguish itself from siblings like get_ohlcv or get_risk_metrics, which may also relate to return-based analysis.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer usage from the tool name and siblings alone.

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