Skip to main content
Glama

rex_session_kill

Terminates a specified Rex session and removes it from the owned set, using a session label or ID to stop it.

Instructions

Kill a session (rex kill) and drop it from the owned set.

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": "<session>"
    },
    "name": "rex_session_kill"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesSession label or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that this is destructive and has a state side effect (removal from the owned set), but it omits irreversibility, whether the session's running actions are terminated, and error behavior for unknown or already-dead sessions.

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 short sentence, front-loaded with the action and resource, with the side effect and CLI alias appended compactly. Nothing is wasted and nothing is buried.

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 destructive tool with no annotations and no output schema, the description covers purpose and one side effect but leaves irreversibility, error semantics, and post-kill state undefined. Adequate, but an agent could still invoke it without knowing the consequences.

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% for the single parameter, whose description already states 'Session label or ID'. The description adds no syntax, format, or default meaning beyond that, so the baseline 3 applies.

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?

Specific verb ('Kill') plus resource ('session'), with the extra scope detail that the session is dropped from the owned set and the CLI equivalent ('rex kill') given for cross-reference. It is clearly distinguishable from rex_session_create and rex_session_view, though it does not explicitly name them.

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?

There is no explicit when-to-use guidance, no statement of prerequisites or preconditions (e.g. confirm the session is idle), and no routing to alternatives such as rex_session_view for inspection before killing. Usage is only inferable from the word 'Kill'.

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