Skip to main content
Glama

Shell status

shell_status
Read-only

Polls a background shell run by run_id and returns its state, exit code, and output tails. Use after launching a command to check completion or wait up to 300 seconds for it to finish.

Instructions

Return the state and output tail of a shell run. wait_seconds (0-300) waits up to that long for it to finish. Use when: after a background shell_run: poll until running=false, then read exit_code. Avoid when: you have no run_id yet. Output: running, exit_code, stdout_tail, stderr_tail. Unknown run_id gives not_found (run ids only live for this session).

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": {
      "run_id": "<run_id>"
    },
    "name": "shell_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesRun id from shell_run.
wait_secondsNoWait up to this many seconds for the run to finish (default 0, max 300). Observation window only, not a timeout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds genuinely new behavior: unknown run_id yields not_found and run ids are session-scoped, plus the clarification that wait_seconds is an observation window rather than a timeout. It stops short of describing output truncation size for the tails, which is the only remaining unknown.

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?

Four short, front-loaded segments (core action, wait semantics, Use when, Avoid when, Output) with no filler. Every sentence carries distinct information an agent needs before calling.

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

Completeness5/5

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

With no output schema, the description compensates by naming the return fields (running, exit_code, stdout_tail, stderr_tail) and the not_found error case, and it flags the session-scoped lifetime of run ids. For a two-parameter polling tool this leaves nothing an agent needs missing.

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%, so both parameters are already documented, including the 0-300 range and the 'not a timeout' caveat. The description's wait_seconds clause largely restates the schema; its added value is the polling instruction, which is usage guidance rather than parameter semantics.

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?

States a specific verb and resource ('Return the state and output tail of a shell run') and implicitly scopes itself against sibling shell_run by referring to runs started in the background. An agent can tell what it fetches without opening the schema.

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

Usage Guidelines5/5

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

Explicit 'Use when' names the prerequisite (after a background shell_run), the polling loop (poll until running=false), and the follow-up (then read exit_code). 'Avoid when: you have no run_id yet' gives an explicit exclusion, so no inference is required.

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