kite-connect-mcp

Refresh the instrument list

refresh_instruments

Idempotent

Download Kite instrument and mutual fund lists into the local cache to repair failed refreshes or add missing new contracts; force both lists to update when needed.

Instructions

Download Kite's instrument list and mutual fund list into the local cache (a few MB). The cache refreshes itself on first use after 08:30 IST each day, so this is only needed after a failed refresh or when a brand-new contract is missing. Returns the same as get_instruments_status plus refreshed (the lists replaced). A list that fails to download keeps its old copy, and the error is shown under last_error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "refresh_instruments"
  }
}

Input Schema

Name	Required	Description	Default
`force`	No	download both lists again even if today's are cached (default: only stale ones)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: payload size (a few MB), the automatic refresh schedule, and partial-failure semantics (a list that fails to download keeps its old copy, error surfaced under last_error). The annotations cover the safety profile, and the description fills in everything else that matters before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, when it is needed, and what happens on failure. The routing-relevant constraint (08:30 IST auto-refresh) is front-loaded and no sentence is redundant.

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 correctly explains the return value (same as get_instruments_status plus `refreshed`) and the failure outcome. For a single-optional-parameter cache-refresh tool, nothing an agent needs to call it correctly is missing.

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 100% and the `force` parameter is already fully documented in the schema (re-download both lists even if today's are cached). The description only indirectly implies the stale-vs-force distinction, so it adds little beyond the schema.

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: downloading Kite's instrument and mutual fund lists into the local cache. It also distinguishes itself from get_instruments_status by saying it returns the same payload plus `refreshed`, so an agent can tell the two apart without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit conditions: only needed after a failed refresh or when a brand-new contract is missing, because the cache self-refreshes on first use after 08:30 IST. This is exactly the when-to-use vs when-not-to-use guidance an agent needs to avoid redundant calls.

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