kite-connect-mcp

WebSocket ticker status

ticker_status

Read-onlyIdempotent

Reports WebSocket ticker state, connection timestamps, reconnect count, subscription modes, cache sizes, and last error. Use it to diagnose why market data streaming stopped or is blocked.

Instructions

The state of the WebSocket ticker: state (idle, connecting, connected, retrying, waiting_for_login, blocked, failed), connected, connected_since, last_message_at (any frame, heartbeats included), last_tick_at, reconnects, subscriptions by mode, how many ticks and order updates are cached, packets_skipped (frames this server could not parse), last_error, and blocked (why the ticker stopped retrying: Kite refused the token, for example because the app has no paid WebSocket plan). Nothing in it is secret.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds real context beyond them — that last_message_at counts heartbeats, that packets_skipped means unparseable frames, that blocked explains why retrying stopped with a concrete example, and that nothing returned is secret — but it says nothing about cost, rate limits, or freshness of the snapshot.

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

Conciseness3/5

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

It is front-loaded with the right noun phrase, but the body is one long comma-chained list with a dangling line break before 'failed', which makes it harder to scan than a short field-grouped structure. Size is defensible only because no output schema exists.

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, the description must enumerate the return fields, and it does so thoroughly, including the meaning of the ambiguous ones. It stops short of saying whether the payload is a single object or whether any fields can be null/omitted when the ticker has never connected.

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?

There are zero parameters, so the baseline is 4. The description correctly spends its words on return semantics instead of inventing parameter guidance.

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 the specific resource (the WebSocket ticker's state) and enumerates what it reports, which lets an agent separate it from ticker_get_ticks, ticker_subscribe, and session_status without opening the schema. It lacks an explicit verb such as 'report' or 'inspect', but the field list pins the purpose down clearly.

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

Usage Guidelines3/5

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

Usage is only implied: the diagnostic fields (blocked, last_error, packets_skipped) hint that this is for troubleshooting connectivity, but the description never says when to call it versus session_status, ticker_get_ticks, or get_safety_status, and never states prerequisites.

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