kite-connect-mcp

Log out of Kite

logout

DestructiveIdempotent

Ends the Kite API session and deletes the stored token, signing out all clients using it. Two-step: the first call previews and returns a confirmation token; call again to confirm.

Instructions

End the Kite API session, delete the stored token and close any open login link (managed auth mode). Two steps: the first call (no confirmation_token) only describes what would happen and returns a confirmation_token; call again with it to do it. Every client using this token is signed out until the next login. It does not log the person out of the Kite web or mobile apps.

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

Input Schema

Name	Required	Description	Default
`confirmation_token`	No	from the first call; omit it to see what would happen and get one

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent, and open-world, so the safety profile is covered. The description adds real value on top: the blast radius ('Every client using this token is signed out until the next login'), the confirmation-token gate, and the explicit scope exclusion for web/mobile apps.

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?

Front-loaded with the core action, then the confirmation protocol, then blast radius, then the scope exclusion. Dense but each sentence carries distinct information; only minor trimming would be possible.

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 single-parameter destructive mutation with no output schema, the description covers action, protocol, side effects, and boundaries. A brief note on what the preview call returns besides the token would close the last gap.

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 coverage is 100% and the schema field already explains 'omit it to see what would happen and get one.' The description restates the same two-step semantics at the call level, adding little parameter-level meaning 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 (end the Kite API session, delete the stored token, close the login link) and immediately distinguishes itself from the login-related siblings by noting it does not affect the Kite web or mobile apps.

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?

Explains the mandatory two-call confirmation protocol clearly: first call without confirmation_token previews, second call executes. It also gives a scope boundary (web/mobile unaffected), but does not explicitly point to session_status or login as the alternative tools for checking or restoring session state.

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