kite-connect-mcp

Stop the WebSocket ticker

ticker_stop

Idempotent

Close the market data WebSocket and clear subscriptions and cached ticks while keeping received order updates; subscribe again to start fresh or retry after token refusal.

Instructions

Close the WebSocket connection and forget all subscriptions and cached ticks (order updates already received stay available). Calling ticker_subscribe later starts afresh, which is also how to retry after Kite refused the connection with the current token. Safe to call when nothing is running.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by naming exactly what is destroyed (subscriptions, cached ticks) and what survives (order updates already received), and by stating the post-call restart semantics. It also reassures that the operation is a no-op-safe call, consistent with idempotentHint=true.

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?

Three tightly packed sentences that front-load the primary effect and then add state and retry context. Nothing is filler, though the retry-after-refused-connection clause is dense enough to slow a quick read.

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?

For a zero-param teardown tool with no output schema, the description covers effect, data retention, safety and the follow-up call. It does not say what the call returns or how to observe that the socket is closed, which ticker_status presumably handles.

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 schema carries no semantic burden and the description correctly spends no words on arguments. Baseline for a no-param tool.

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 ('Close the WebSocket connection') plus the scope of the reset ('forget all subscriptions and cached ticks'). An agent can distinguish it from ticker_unsubscribe and ticker_status from this sentence alone.

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 explicit conditions: safe to call when nothing is running, and ticker_subscribe is the way back / retry path after a refused connection. The one gap is it never contrasts itself with ticker_unsubscribe, the closest sibling, leaving the agent to infer that boundary.

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