kite-connect-mcp

OHLC quotes

get_ohlc

Read-onlyIdempotent

Fetch last price and OHLC data for up to 1,000 instruments in one call, plus a list of instruments with no available data.

Instructions

Last price and the day's open / high / low / close (close is the previous session's close) for up to 1000 instruments in one call, in INR. Returns {"quotes": {instrument: {instrument_token, last_price, ohlc}}, "missing": [...]} (missing: instruments Kite has no data for). Lighter than get_quotes: no depth, volume or open interest. Needs the paid Kite Connect plan.

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

Input Schema

Name	Required	Description	Default
`instruments`	Yes	1 to 1000 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?

Goes well past the annotations: discloses the response shape (quotes/missing), explains that `missing` holds instruments Kite has no data for, and flags the paid-plan requirement and INR denomination. The annotations already cover read-only/idempotent safety, and the description adds the failure handling and account-tier constraints an agent needs before calling.

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-loads what the tool returns and the 1000-instrument scope, then the comparison to get_quotes and the plan requirement. The inline JSON return sketch and backtick explanation are slightly dense but each carries real information; little could be cut without losing value.

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 only one parameter and no output schema, the description supplies exactly what is missing: the return structure including the `missing` bucket, the currency, and the plan prerequisite. Nothing an agent needs to invoke it correctly is absent.

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 itself supplies the EXCHANGE:TRADINGSYMBOL format with examples. The description only restates the 1000-instrument cap and the INR unit, adding no new parameter-level meaning, so the baseline 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+resource (last price and day's OHLC for up to 1000 instruments), names the currency (INR), and explicitly positions itself against the closest sibling: "Lighter than get_quotes: no depth, volume or open interest." An agent can distinguish it from get_quotes and get_ltp without opening a schema.

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?

Gives clear selection context by contrasting with get_quotes (no depth/volume/OI) and states a hard prerequisite, the paid Kite Connect plan. It stops short of an explicit "use get_quotes when you need depth/OI" directive and never mentions get_ltp, which is also a close alternative, so it is strong but not exhaustive.

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