Skip to main content
Glama

codebuddy_job_status

Read the current lifecycle and execution status of a CodeBuddy background job by job ID, so you can monitor progress and confirm whether a dispatched task is still running, completed, or failed.

Instructions

Read the current lifecycle and execution status of a CodeBuddy background job.

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": "codebuddy_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. "Read" implies a non-mutating call, but nothing is said about whether the call blocks or polls, what the possible status values are, what happens for an unknown or expired jobId, or whether the read is bounded to the caller's jobs.

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?

One short sentence with the resource and scope front-loaded and no filler. It is efficient, but its brevity comes at the cost of the context a status tool needs.

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

Completeness2/5

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

A status tool's usefulness hinges on what status values mean and whether the result is a snapshot or a poll, and there is no output schema to cover that. With no annotations and no parameter documentation, the definition leaves the agent under-equipped to interpret the response.

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

Parameters2/5

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

Schema description coverage is 0% for the single required jobId parameter, so the description must compensate and does not. It never states where jobId comes from (presumably a start response) or what form it takes, leaving the only parameter undocumented in both schema and prose.

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 ("Read") and a specific resource ("current lifecycle and execution status of a CodeBuddy background job"). This cleanly separates it from transcript/stop/reply siblings by implication, though it never names an alternative to reinforce the distinction.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus codebuddy_job_transcript, codebuddy_stop_job, or codebuddy_reply_job, and no mention of prerequisites such as having a jobId from a start call. Any usage pattern must be inferred from the name alone.

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