ChannelTerm

Overview Schema Source Related Servers Discussions Admin

Close Terminal Session

terminal_close

Destructive

Closes a shared terminal session for all attached clients and releases its transport. Use it to end collaboration fully; detach one client instead when the session should stay open.

Instructions

Close the shared terminal Session for every attached client and release its transport; use terminal_session_detach to record only one client's departure without closing 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": {
      "session_id": "<session_id>"
    },
    "name": "terminal_close"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Active Session ID or short reference.

Output Schema

Name	Required	Description	Default
`closed`	Yes
`session_id`	Yes
`session_ref`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.2Oct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds the crucial blast radius (affects every attached client, not just the caller) and the transport-release side effect. It stops short of stating whether an active lease must be held or released first, which matters in a toolset full of lease tools.

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?

One sentence, front-loaded with the destructive scope, then the disambiguating alternative. No filler or redundant restatement of the title.

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?

An output schema exists so return values need no explanation, and the scope/alternative relationship is fully covered. Remaining gap is prerequisite context (lease ownership or authorization) for a destructive multi-client operation, which the description leaves implicit.

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 sole parameter's schema text already defines it as an active session ID or short reference. The description adds no format, validation, or lookup guidance beyond that, so baseline 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?

Specific verb and resource ("Close the shared terminal Session") plus explicit scope: "for every attached client and release its transport." The contrast with terminal_session_detach makes it unambiguous against the nearest sibling.

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?

Names the alternative (terminal_session_detach) and the exact condition that selects it: "to record only one client's departure without closing it." When-to-use and when-not-to-use are both stated outright.

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

Deploy Server