kite-connect-mcp

Full market quotes

get_quotes

Read-onlyIdempotent

Fetches full market snapshots for up to 500 instruments, including price, volume, OHLC, open interest, circuit limits and five-level depth, and lists any instruments with no data.

Instructions

Full market snapshot for up to 500 instruments in one call: last_price, last_quantity, volume, average_price, buy_quantity / sell_quantity, ohlc (close is the previous session's close), net_change, oi / oi_day_high / oi_day_low (F&O), lower / upper circuit limits and the 5-level market depth (buy / sell price, quantity, orders). Prices are in INR, timestamps in IST. Returns {"quotes": {instrument: snapshot}, "missing": [...]}: missing lists requested instruments Kite has no data for (misspelt, expired or not traded). Needs the paid Kite Connect plan; quote calls are limited to 1 per second. A full quote with depth is about 1.5 KB: for many instruments use get_ltp or get_ohlc.

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": {
      "instruments": "<instruments>"
    },
    "name": "get_quotes"
  }
}

Input Schema

Name	Required	Description	Default
`instruments`	Yes	1 to 500 instruments, each EXCHANGE:TRADINGSYMBOL (e.g. "NSE:INFY", "NSE:NIFTY 50", "NFO:NIFTY25NOVFUT")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say read-only/idempotent/open-world; the description adds the subscription-tier requirement (paid Kite Connect), a concrete rate limit of 1 call per second, per-quote payload size, currency (INR), and IST timestamps. It also explains the `missing` behavior for misspelt, expired, or untraded instruments, which is real operational context an agent needs.

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?

Front-loaded with the field inventory, then return shape, then operational constraints and alternatives — a sensible priority order with no filler. It is a single dense paragraph that is long but nearly every clause carries a fact.

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

Completeness5/5

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

With no output schema, the description fully describes the return shape {quotes, missing} and what `missing` means, plus cost, rate, and units constraints. Nothing an agent needs to call this correctly or interpret the reply is left unstated.

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 coverage is 100% and the schema already documents the EXCHANGE:TRADINGSYMBOL format, the 1–500 bounds, and examples. The description reinforces the 500 cap and explains that unrecognized instruments land in `missing`, but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (full market snapshot for up to 500 instruments) and enumerates the exact fields returned, from last_price and depth to circuit limits and OI. It also names the sibling tools get_ltp and get_ohlc, so an agent can place it precisely among the quote tools.

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

Usage Guidelines4/5

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

Explicitly routes bulky requests to get_ltp or get_ohlc by noting a full quote is ~1.5 KB, and notes the 1/second call limit and paid-plan requirement, which shapes when this tool is practical. It does not say outright when this tool is the right choice (e.g. 'use when you need depth or volume'), leaving that inference to the reader.

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