Skip to main content
Glama

Wait for command

bash_await
Read-onlyIdempotent

Wait for a background shell command (by shell_id) to finish and return its output.

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": {
      "shell_id": "<shell_id>"
    },
    "name": "bash_await"
  }
}

Input Schema

NameRequiredDescriptionDefault
shell_idYes
project_idNoProject id (or use session from use_project)
timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the call blocks until completion and returns output, but it is silent on timeout behavior, partial output on timeout, and whether calling it on an already-finished shell is safe — all material for a blocking wait primitive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly written sentence with the key identifier front-loaded and no filler. Brevity is appropriate here, though the sentence could carry one more clause (timeout behavior) at almost no cost.

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?

With no output schema and no annotations covering timeout, the description should explain what 'return its output' looks like when the wait times out or when the process failed. As written it covers the happy path only, which is thin for a blocking tool exposed to agent loops.

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 only 33%: shell_id and timeout_ms are undocumented in the schema. The description clarifies only that shell_id refers to a background shell command, and says nothing about timeout_ms (default value, units, or what result a timeout produces), leaving the most ambiguous parameter unexplained.

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?

States a concrete verb and resource: waits on a background shell command identified by shell_id and returns its output. That separates it in spirit from the launch-style sibling 'bash', but the description never names that sibling or explicitly says 'for commands started in the background by bash', so differentiation is implied rather than stated.

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?

The phrase 'background shell command (by shell_id)' implies you call this after launching a background job, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., what to do instead if the command is expected to finish quickly).

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