Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_peer_comparison

Compare NSE/BSE peer stocks side by side on one selected metric as of a specified date, enabling relative performance analysis without future data leakage.

Instructions

Side-by-side comparison of NSE/BSE peers on one metric.

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": {
      "symbols": "<symbols>"
    },
    "name": "get_peer_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
metricNoreturn_20d
symbolsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden but discloses almost nothing: it does not state that this is a read-only lookup, how missing or invalid symbols are handled, or how the comparison is structured. The existence of an output schema reduces the need to describe return values, but the interaction behavior remains opaque.

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?

A single front-loaded sentence with no wasted words and a clear scope statement. Its brevity is efficient rather than padded, though it tips into under-specification rather than crispness.

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?

For a three-parameter tool with zero schema documentation, the description is too thin to be safe to call blind. It omits metric vocabulary, symbol formatting, and date semantics, all of which the agent needs and cannot get from structured fields.

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 for all three parameters and largely fails. 'Peers' loosely maps to `symbols` and 'on one metric' loosely maps to `metric`, but the default (return_20d), accepted metric names, symbol format, and the meaning of `as_of` are never explained.

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?

States a concrete operation (side-by-side comparison) on a concrete resource (NSE/BSE peers) scoped to a single metric. An agent can tell this is a comparative analytics lookup rather than a raw data fetch like get_ohlcv, though the definition never explicitly names the siblings it differs from.

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 choose this over get_returns, get_risk_metrics, or get_technical_indicators, nor any prerequisite on how many symbols are required or whether they must be from the same exchange. The agent must infer all routing decisions from context.

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