Skip to main content
Glama

workbench_close_case

Closes a case's upstream sessions and releases subprocesses while retaining original evidence. New calls create new sessions; old upstream IDs and target state are not restored.

Instructions

Close this case’s two upstream sessions and release subprocesses. Retains original evidence. New calls create new sessions; old upstream IDs and target state are not restored.

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": {
      "case_id": "<case_id>"
    },
    "name": "workbench_close_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description goes further by disclosing exactly what is terminated (two upstream sessions plus subprocesses), what survives (original evidence is retained), and what is not recoverable (old upstream IDs and target state are not restored). That irreversibility note is the key behavioral fact an agent needs and is not derivable from the annotations. It does not cover permission requirements or behavior when the case is already closed, so it is not a full 5.

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?

Three short sentences, no filler, and the core action is front-loaded ahead of the retention and irreversibility caveats. Every clause carries distinct information an agent would otherwise lack.

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 one-parameter lifecycle tool with no output schema, the description covers action, side effects, data retention and non-reversibility, which is most of what is needed to call it safely. The remaining gaps are error/idempotency behavior (what happens if the case is already closed) and the return value, which matter less here.

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 0%, so the burden falls on the description, which only refers to "this case's" sessions without explaining what case_id identifies or whether it must be an open case. With a single obviously named UUID parameter and a strict pattern in the schema, the risk of misuse is low, so this lands at adequate rather than deficient.

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 gives a specific verb+resource ("Close this case") and scopes it precisely: two upstream sessions closed and subprocesses released. That is far more informative than a bare "close case" and lets an agent distinguish it from lifecycle siblings like workbench_create_case or workbench_status. It stops short of naming any sibling it should not be confused with.

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?

Usage is implied by the lifecycle framing (closing a case when done) but never stated: there is no "use when you are finished with the case" clause and no named alternative for partial shutdown or cleanup. The second half of the description is a consequence warning rather than when-to-use guidance, so the agent must infer the trigger condition.

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