Skip to main content
Glama

Coline

Stop a Code session

stop_code_session
DestructiveIdempotent

Stops a running Code session. Its work so far stays; use it when the person wants the work to stop.

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": {
      "workspace": "<workspace>",
      "sessionId": "<sessionId>"
    },
    "name": "stop_code_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesCode session id from list_code_sessions.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
planYes
taskYes
stateYes
checksYes
projectYes
sessionIdYes
previewUrlYes
statusLineYes
changeRequestUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds the important behavioral fact that the session's work is preserved ("Its work so far stays"), which qualifies what 'destructive' actually means here. It does not cover permissions or what happens when the session is already stopped, but the annotation coverage lowers the burden.

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?

Two short sentences with zero filler: the action is stated first, then the consequence, then the usage cue. Every sentence earns its place.

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 two-parameter destructive action with full schema coverage and an output schema, the description supplies the crucial outcome (work is retained) and a usage cue. It is nearly complete; only error/idempotency behavior for an already-stopped session is left 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 description coverage is 100%, with both sessionId (source: list_code_sessions) and workspace (source: workspaces.list) fully documented in the schema. The description adds no further parameter meaning, 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?

"Stops a running Code session" gives a specific verb (stops) plus resource (Code session), which clearly separates it from read-oriented siblings such as get_code_session or list_code_sessions. It stops short of naming a sibling or a boundary case, so it is clear but not maximally differentiated.

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?

"Use it when the person wants the work to stop" implies a usage context, but gives no explicit when-not condition, no prerequisites (e.g. session must be running), and points to no alternative for related actions like inspecting or keeping a session. The guidance is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources