Skip to main content
Glama

Get Command Status

get_command_status

Retrieves the status and output of an asynchronous SSH command using its command ID, so you can monitor completion and collect results.

Instructions

Get the status and output of an async command.

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": {
      "command_id": "<command_id>"
    },
    "name": "get_command_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYesThe command ID returned by execute_command_async

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2+p1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says it returns status and output. It is silent on whether calls are non-destructive, whether polling repeatedly is safe, whether output is cumulative or consumed, and whether the call blocks until completion.

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?

A single front-loaded sentence with no filler; every word earns its place.

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?

For a one-parameter read tool with no output schema this is close to sufficient, but the absence of any polling/blocking semantics or terminal-state description leaves a real gap for an agent deciding how to call and re-call it.

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% and the single parameter already documents itself as the ID returned by execute_command_async. The description adds no additional meaning about ID format or behavior on an unknown/completed ID, so this is baseline.

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 specific verb and resource: retrieve status plus output for an async command. The pairing with execute_command_async is implied through the schema's command_id reference, though the description text itself does not name a sibling or exclude list_running_commands / list_command_history.

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 only implied: the schema note that command_id is 'returned by execute_command_async' sketches the follow-up flow after an async launch. There is no explicit when-to-use or when-not-to-use statement distinguishing this from list_running_commands or list_command_history.

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