Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_chart_patterns

Detect candlestick patterns and support/resistance levels for Indian stocks across a lookback window, optionally as of a date, to avoid future data.

Instructions

Candlestick patterns (hammer, doji, engulfing, stars) + support/resistance.

``window`` = trailing-bar scan width for the candlestick detector
(default 20). A pattern older than the last ``window`` bars cannot be
reported — raise ``window`` to look further back (bounded by lookback_days).

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

Input Schema

NameRequiredDescriptionDefault
as_ofNo
symbolYes
windowNo
lookback_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose a genuine behavioral constraint — that patterns older than the last window bars cannot be reported and window is bounded by lookback_days. It says nothing about cost, rate limits, or how as_of affects the scan start, leaving part of the behavioral picture undisclosed.

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?

Output content is front-loaded in one line, then a focused paragraph on the only non-obvious parameter. No filler; the odd backtick markup is cosmetic rather than wasteful.

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 no explanation, and the window/lookback interaction is well covered. However, the as_of parameter is left undefined and there is no routing guidance against the overlapping technical-indicators sibling, which is a real gap for a four-parameter analysis tool.

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% across four parameters, so the description must compensate. It does an excellent job on window (default 20, trailing-bar scan width, must raise to look further back) and ties it to lookback_days, but symbol and especially as_of receive no explanation at all.

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 specific resource and enumerates the pattern types detected (hammer, doji, engulfing, stars) plus support/resistance, so an agent knows exactly what comes back. It does not differentiate itself from the sibling get_technical_indicators, which plausibly overlaps, so it stops short of a 5.

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 by the output content (candlestick/support-resistance analysis), and the window paragraph explains a tuning scenario, but there is no explicit statement of when to pick this over get_technical_indicators or get_ohlcv, and no exclusions.

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