kite-connect-mcp

Instrument details

get_instrument

Read-onlyIdempotent

Fetch a Kite instrument by EXCHANGE:TRADINGSYMBOL or instrument token to check lot size, tick size, expiry, and strike before placing an order.

Instructions

One instrument from Kite's daily instrument list: key, instrument_token, exchange_token, tradingsymbol, name, exchange, segment, instrument_type (EQ, FUT, CE, PE), expiry, strike, lot_size, tick_size (INR) and last_price (from the daily dump, not live). Use it to check the lot size and tick size before an order.

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": {
      "instrument": "<instrument>"
    },
    "name": "get_instrument"
  }
}

Input Schema

Name	Required	Description	Default
`instrument`	Yes	EXCHANGE:TRADINGSYMBOL (e.g. "NSE:INFY", "NSE:NIFTY 50", "NFO:NIFTY25NOVFUT") or a numeric instrument_token (e.g. 408065)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context — the data is a daily snapshot, so last_price is stale — which matters for trading decisions. It does not say how to refresh that snapshot (refresh_instruments) or what happens for an unknown symbol.

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 core statement, then a compact field list, then the use case. The field enumeration is long but serves a real purpose since there is no output schema. Only the '(EQ, FUT, CE, PE)' and '(INR)' parentheticals are borderline filler.

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

Completeness4/5

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

With no output schema, listing the returned fields is exactly the right compensation and the staleness caveat is important. Remaining gaps — unknown-instrument error behavior, and the relationship to refresh_instruments/search_instruments — are modest for a single-parameter read 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 coverage is 100% and the schema's own description already explains both accepted forms (EXCHANGE:TRADINGSYMBOL or numeric instrument_token) with examples. The description adds nothing about the parameter beyond that, so it earns the baseline rather than more.

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 verb/resource ('One instrument from Kite's daily instrument list') and enumerates the returned fields, so the agent knows exactly what it gets back. It does not explicitly name the sibling it differs from (search_instruments), leaving the differentiation implicit.

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 a concrete use case — 'check the lot size and tick size before an order' — and signals when not to rely on it by noting last_price is from the daily dump, not live (pointing toward quote/LTP siblings). It stops short of naming those alternatives or stating prerequisites.

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