kite-connect-mcp

Stop streaming instruments

ticker_unsubscribe

Idempotent

Stop streaming selected instruments and clear their cached ticks while keeping the WebSocket open for order updates. Unsubscribed items are returned for easy verification.

Instructions

Stop streaming instruments and drop their cached ticks. Instruments that were not subscribed are listed under not_subscribed. The WebSocket connection stays open (order updates keep arriving); ticker_stop closes it.

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": {
      "instruments": "<instruments>"
    },
    "name": "ticker_unsubscribe"
  }
}

Input Schema

Name	Required	Description	Default
`instruments`	Yes	EXCHANGE:TRADINGSYMBOL names (NSE:INFY, NSE:NIFTY 50, NFO:NIFTY25NOVFUT) and/or numeric instrument tokens (408065). Names are looked up in the instrument list; if that cannot be loaded, use tokens.

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?

Even though the annotations already declare the safety profile (destructiveHint=false, idempotentHint=true), the description adds real behavioral context: cached ticks are dropped, instrument names that were not subscribed are returned under not_subscribed, and the WebSocket connection survives so order updates keep flowing. That is exactly the 'what gets affected / what stays alive' context that annotations cannot convey.

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 short sentences, front-loaded with the action and its effect, then the return-value note, then the sibling contrast. No filler and no repetition of the tool title.

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?

For a single-parameter tool with no output schema, the description covers the action, the side effect, the partial-success return (not_subscribed), and the connection semantics. An agent has everything it needs in order to call this tool correctly and interpret the result.

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 schema documents the accepted formats (EXCHANGE:TRADINGSYMBOL or numeric token) plus the 3000-item limit. The description adds nothing about the parameter beyond what the schema already says, so the baseline of 3 applies.

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 uses a specific verb and resource ("stop streaming instruments") and immediately names the related side effect ("drop their cached ticks"). It is clearly distinguishable from ticker_subscribe and ticker_stop, which the description calls out by name.

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?

This description explicitly says when to use this tool rather than the alternative: it states that it unsubscribes individual instruments while the WebSocket connection stays open, and that ticker_stop closes the connection. That is an explicit alternative plus the condition that selects it, leaving nothing to inference.

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