Skip to main content
Glama

codebuddy_reply_job

Sends input to a waiting CodeBuddy job and shows approval-related requests to the user before replying.

Instructions

Reply to a CodeBuddy job that is waiting for input. Show approval-related requests to the user before replying.

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>",
      "text": "<text>"
    },
    "name": "codebuddy_reply_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses one useful trait — surface approval-related requests to the user first — but says nothing about whether the reply resumes the job, whether the call blocks, what happens on an invalid or stale jobId, or what a successful reply returns.

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?

Two short sentences, front-loaded with the action and its precondition, with no filler. It is efficient, though the brevity comes at the cost of the parameter and behavior detail noted elsewhere.

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?

With no annotations, no output schema, and zero parameter documentation, the description is the only source of context and it covers only the trigger condition. For a mutation-style tool that sends content into a running job, an agent needs more about parameter sourcing and post-call effects than is provided.

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 two required parameters, and the description never mentions 'jobId' or 'text'. It does not say where the jobId comes from (presumably codebuddy_job_status) or what form the reply text should take, so the agent gets no meaning beyond the bare types and minLength constraints.

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?

The description gives a specific verb and resource ('Reply to a CodeBuddy job') plus a qualifying state ('waiting for input'), which is enough to distinguish it from status/transcript/stop siblings. It stops short of naming any sibling explicitly, so the differentiation is inferred 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 precondition 'job that is waiting for input' is a real when-to-use signal, and the approval-handling sentence adds a procedural rule. However, there is no guidance on when NOT to use it or which sibling to prefer (e.g., workbuddy_answer_permission or clawbridge_reply for other reply flows), leaving the agent to guess at boundaries.

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