Skip to main content
Glama

close_session

Terminate an active Detour session using its session_id from open_session or list_sessions, ending that SSH connection and freeing its resources.

Instructions

Close a session of yours.

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

Input Schema

NameRequiredDescriptionDefault
session_idYesA session_id from open_session or list_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and "close" is doing very little work. It does not say whether closing is irreversible, what happens to running commands or tunnels inside the session, whether it must already be closed/idle, or whether it can fail for lack of access — all critical for a destructive lifecycle operation.

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?

One short, front-loaded sentence with zero filler or redundancy. It is arguably under-specified rather than bloated, but on the conciseness axis it is clean and easy to parse.

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

Completeness3/5

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

For a one-parameter lifecycle tool with fully documented schema, the definition is minimally viable — an agent knows which ID to pass. But with no annotations and no output schema, the description should compensate by saying what closing entails and what is lost; it does not.

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 single parameter is documented with a meaningful provenance hint ("from open_session or list_sessions"), so the structured data does the heavy lifting. The description adds no meaning beyond the schema, which is the baseline-3 case for high coverage.

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?

"Close a session of yours" gives a specific verb (close) and resource (session), and the possessive "of yours" usefully scopes it to the caller's own sessions rather than any session. It is clearly not a duplicate of open_session or list_sessions, but it never names those siblings or states the inverse relationship explicitly.

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

Usage Guidelines3/5

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

The description implies the use case (tear down a session you own), and the schema's mention of "a session_id from open_session or list_sessions" hints at the workflow. However, there is no explicit when-to-use guidance, no mention of when not to close, and no usage guidance in the description text itself — that hint lives in the parameter schema, not here.

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