Skip to main content
Glama

Stop DSH SDK runtimes

dsh_shutdown

Stops all SDK runtimes started by the bridge and abandons active turns; the next start launches a fresh runtime.

Instructions

Stop every SDK runtime this bridge started. Active turns are abandoned (the SDK protocol has no per-turn cancel); the next dsh_start spawns a fresh runtime.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dsh_shutdown"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations the description carries the full load, and it delivers the two most important facts: active turns are abandoned because the SDK protocol offers no per-turn cancel, and the next dsh_start creates a fresh runtime rather than resuming. It omits whether the call is idempotent when no runtimes are running and whether any confirmation or error is returned, which are the remaining behavioral unknowns.

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 sentences, both front-loaded with the most decision-relevant information (the stop action, then the abandonment caveat). There is no filler, and the parenthetical about the missing cancel API is exactly the kind of context that 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 zero-parameter, mutation-like lifecycle tool with no output schema, the definition covers purpose, the destructive side effect on active turns, and the follow-on state. It leaves open only minor operational details (behavior when nothing is running, whether success is reported), which is acceptable given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. Noting that the scope covers every runtime the bridge started does usefully confirm the absence of a selective parameter, but there is no further parameter meaning to add.

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?

"Stop every SDK runtime this bridge started" gives a specific verb and a precisely scoped resource, so there is no ambiguity about breadth (all runtimes owned by this bridge, not all runtimes globally). No sibling competes with it for the stop operation, so no disambiguation sentence is needed.

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

Usage Guidelines4/5

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

The description implicitly places the tool in the lifecycle by noting that after it runs, "the next dsh_start spawns a fresh runtime," which tells an agent this is end-of-session cleanup before a restart. It does not state an explicit when-not or say what to use instead if the agent only wants to close one session, so guidance is contextual rather than complete.

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