Skip to main content
Glama
Sign In
kite-connect-mcp

kite-connect-mcp

by techfreakworm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Instrument list status

get_instruments_status
Read-onlyIdempotent

Check local instrument and mutual fund cache status without contacting Kite, including load state, row counts, staleness, next refresh time, and last refresh error.

Instructions

What the local instrument cache holds: for the instrument list and the mutual fund list, whether it is loaded, row counts (per exchange for the instrument list), when it was loaded, whether it is stale (Kite publishes a new dump every day around 08:30 IST), when it will next be refreshed and the last refresh error, if any. Never contacts Kite.

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": "get_instruments_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: no network contact with Kite, the daily ~08:30 IST dump schedule, and the exposure of the last refresh error. One mild tension exists in that openWorldHint=true while the description says it never contacts Kite; it is not a direct contradiction of the read/write hints.

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?

The content is front-loaded with the subject ('What the local instrument cache holds') and every clause carries information. It is a single dense sentence with nested parentheticals that is slightly harder to scan than a short bulleted breakdown would be.

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?

There is no output schema, so the description must describe return values itself, and it does so comprehensively, including per-exchange row counts and error reporting. For a zero-parameter status tool this covers everything an agent needs to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit. The description correctly spends its space on return-value semantics instead.

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?

The description names the specific resource (the local instrument cache) and enumerates exactly what is reported: loaded state, row counts per exchange, load time, staleness, next refresh, and last error. This is clearly distinguishable from sibling tools like refresh_instruments or search_instruments.

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?

Usage is strongly implied by the freshness/staleness framing, which gives an agent the context needed to decide whether a refresh is warranted. However, it never names refresh_instruments as the follow-up alternative or states an explicit 'use this before X' condition, so it falls short of a 5.

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

Deploy Server

Other Tools