Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_technical_indicators

Calculate RSI, SMA, EMA, MACD, Bollinger Bands, ATR, and VWAP for an Indian stock as of a chosen date so you get reliable Python-computed values instead of LLM-calculated math.

Instructions

RSI/SMA/EMA/MACD/Bollinger/ATR/VWAP computed in Python, never LLM math.

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

Input Schema

NameRequiredDescriptionDefault
as_ofNo
symbolYes
indicatorsNo

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?

No annotations are supplied, so the description carries the full behavioral burden. The 'computed in Python, never LLM math' clause is a useful accuracy guarantee, but nothing is said about default behavior when the indicators list is null, what happens for unknown indicator names, or what happens when as_of is omitted.

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 short sentence with the substantive content (the indicator list) front-loaded and zero filler. It is telegraphic rather than complete, but no words are wasted.

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

Completeness3/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 values need not be explained, and the delivery-mechanism claim is a genuine addition. Still, for a three-parameter tool with no schema descriptions, the missing semantics for `as_of` and the default indicator set leave gaps an agent must guess at.

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 description coverage is 0%, so the description must compensate. It does add real value by naming likely valid values for the `indicators` array, but `symbol` and especially `as_of` (format, timezone, default-to-now behavior) remain completely undefined.

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 concretely by listing the indicator set (RSI/SMA/EMA/MACD/Bollinger/ATR/VWAP), so an agent can infer this returns technical indicator values. However, there is no explicit verb or scope statement such as 'compute indicator series for a symbol over a date range', and no direct differentiation from siblings like get_ohlcv or get_risk_metrics.

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 call this versus get_ohlcv, get_returns, or get_risk_metrics, and no mention of prerequisites such as a valid symbol or required history window. Usage must be inferred entirely from the indicator list.

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