claude-code-mcp

Overview Schema Source Related Servers Discussions Admin

claude_code_session

Destructive

Manage Claude Code sessions: list active sessions, inspect details, cancel or interrupt running sessions to control autonomous coding tasks.

Instructions

List, inspect, cancel, or interrupt sessions.

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": {
      "action": "<action>"
    },
    "name": "claude_code_session"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Session operation: list, get, cancel, or interrupt.
`sessionId`	No	Required for get/cancel/interrupt.
`includeSensitive`	No	Default: false. Exposes more session fields, but some secrets remain redacted.

Output Schema

Name	Required	Description	Default
`isError`	No
`message`	No
`sessions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.3Jul 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations provide destructiveHint: true, indicating destructive actions. The description mentions cancel and interrupt, but does not clarify differences or side effects. With annotations, the description adds no extra behavioral context.

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?

Very concise single sentence, front-loaded with verbs. Could be structured better for multi-action tools, but not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given multiple actions and an output schema, the description should detail what each action does and prerequisites (e.g., sessionId required for get/cancel/interrupt). Missing these details makes it incomplete for a complex tool.

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%; parameters are well-documented in the schema. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states the tool manages sessions with actions like list, inspect, cancel, or interrupt. It distinguishes from sibling tools like 'claude_code_check' or 'claude_code_reply' which focus on other aspects.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs siblings, or when to choose one action over another. For a tool with multiple distinct actions, such guidance is missing.

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

Deploy Server