Skip to main content
Glama

Job status

job_status
Read-onlyIdempotent

Check a background command's status and exit code after waiting up to 50 seconds, avoiding tight polling. Use tail lines to confirm progress and full logs for complete output.

Instructions

Check the status of a background command started by run_command with wait=. Returns status (running/completed/timeout/failed), exit_code and duration. DO NOT poll in a tight loop. Pass waitSec (1-50): the server holds the answer until the job finishes or the time runs out, so one call replaces dozens. Pass tailLines to see the last lines of output and confirm real progress. Use job_output for the full log.

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": {
      "jobId": "<jobId>"
    },
    "name": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
jobIdYes
waitSecNo
tailLinesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses the long-polling behavior, the 1–50 second wait range, and the warning against tight polling. It also documents the possible status values and returned fields, which is especially useful because no output schema is supplied.

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?

The description is front-loaded with its purpose, then moves efficiently through outputs, polling behavior, optional parameters, and the full-log alternative. Every sentence contributes operational information without filler or unnecessary repetition.

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 read-only status tool, it covers the prerequisite command, efficient invocation strategy, important optional parameters, returned information, and the alternative for complete output. Minor omissions remain, principally the exact source of jobId and details such as duration units or when exit_code is unavailable.

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?

With only 40% schema description coverage, the description meaningfully explains the otherwise undocumented waitSec parameter, including its range and blocking semantics, and tailLines, including its diagnostic purpose. It does not explicitly state that jobId is the identifier returned by run_command, leaving a small gap for the central required parameter.

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?

The opening sentence specifies both the operation and resource: checking a background command job started by run_command with wait=<seconds>. The closing sentence also distinguishes it from job_output, which is intended for retrieving the full log.

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?

It gives concrete invocation guidance: use waitSec for server-held waiting instead of tight polling, use tailLines to inspect recent output and confirm progress, and use job_output when the full log is needed. These instructions cover both efficient usage and selection of the appropriate sibling tool.

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