Skip to main content
Glama

clawbridge_refresh

Refresh a dispatched task's status from its CodeBuddy job to map observed state to the recorded lifecycle without estimating progress.

Instructions

Refresh a dispatched task from its CodeBuddy job. This maps observed job state to a recorded lifecycle without estimating progress.

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": {
      "taskId": "<taskId>"
    },
    "name": "clawbridge_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuinely useful trait: the mapping is deterministic and does not estimate progress. It leaves the important questions unanswered, though — whether recorded lifecycle state is mutated and whether the operation is idempotent or safe to repeat, plus authorization and failure behavior.

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 tight sentences, front-loaded with the action and its source, with no filler. The second sentence is a meaningful behavioral qualifier rather than padding, though the whole definition is arguably under-specified for a refresh/mutation operation.

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 single-parameter tool with no output schema and no annotations, the definition covers what it does but not what happens as a result — what a refresh returns, what lifecycle states can be recorded, or how it fails when the CodeBuddy job is missing or unreachable. Adequate but with clear gaps.

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% and the description never mentions taskId, so no meaning is added beyond the schema's UUID format and pattern. The only implicit constraint is that the task must be dispatched, which follows from the tool's purpose rather than from any parameter documentation.

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 ('refresh'), a specific resource ('a dispatched task'), and the external source ('from its CodeBuddy job'), so the purpose is unambiguous. It does not differentiate itself from close siblings such as codebuddy_job_status or clawbridge_status, which appear to observe similar job state, leaving an agent to infer which one to call.

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 implied rather than stated: the task must already be 'dispatched' and have an associated CodeBuddy job, which is a precondition an agent can infer. There is no explicit when-to-use versus when-to-use-an-alternative guidance and no mention of what to do when a task has no job or is in a terminal state.

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