Skip to main content
Glama

clawbridge_logs

Retrieve bounded recent worker transcript events for a dispatched task to monitor progress and diagnose issues, with model thoughts and oversized content filtered out.

Instructions

Read bounded recent worker transcript events for one dispatched task. Model thought events and oversized content are filtered by the CodeBuddy client.

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_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully discloses that output is bounded to recent events and that model-thought events and oversized content are filtered client-side, but says nothing about ordering, limits, failure behavior for unknown/undispatched task IDs, or that it is strictly read-only.

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?

Two short sentences, front-loaded with the core action and followed immediately by the filtering caveat. No filler.

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 annotations and no output schema, the description covers purpose and filtering but leaves return shape, result bounds, and error conditions unstated. "Bounded" and "recent" are never quantified.

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?

Schema coverage is 0% for the single taskId parameter, so the description must compensate. It does convey that the ID identifies a dispatched task whose transcript is being read, which is meaningful framing, but does not say where to obtain that ID or what happens for non-dispatched tasks.

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: "Read bounded recent worker transcript events for one dispatched task." Scope (one task, recent, bounded, worker transcript) is precise enough to separate it from generic event-listing siblings, though it never names a counterpart tool explicitly.

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 by the phrase "for one dispatched task" — an agent can infer this is for inspecting a specific dispatched task rather than browsing events. There is no statement of when to prefer it over the sibling event/transcript tools or what preconditions must hold.

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