Skip to main content
Glama

clawbridge_tasks

List compact durable task records filtered by project or lifecycle state to monitor dispatched development tasks, with status reported as recorded lifecycle state rather than progress percentage.

Instructions

List compact durable task records. Status is a recorded lifecycle state, not an estimated progress percentage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clawbridge_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
projectIdNo
executionStateNo

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, yet it discloses little beyond the tool being a read/list operation. The one substantive disclosure is that status is a recorded lifecycle state rather than an estimated progress percentage, which usefully prevents misinterpretation of the executionState values, but ordering, pagination, scope, and what 'compact' omits are all unstated.

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 with no filler, and the purpose statement leads before the clarifying caveat. It is efficiently structured, though the brevity borders on under-specification for a tool with three undocumented parameters.

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 0% parameter description coverage, the definition is thin for a three-parameter listing tool. An agent cannot learn whether results are ordered, paginated, filtered client-side, or what fields each record contains, and the relationship to sibling listing tools is unaddressed.

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

Parameters3/5

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

Schema description coverage is 0% across three parameters, so the description would need to compensate. It adds meaning only indirectly by framing status as a recorded lifecycle state, which helps interpret the executionState enum; limit and projectId are left entirely to their bare schema types, and no default or filtering semantics are explained.

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?

'List compact durable task records' gives a specific verb (List) plus resource (task records), so an agent knows the operation type immediately. It does not distinguish this from near neighbors such as clawbridge_status, clawbridge_events, or clawbridge_projects, and 'compact durable' is unexplained jargon.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives among the many sibling task/status tools. The only guidance-like statement clarifies what the status field means, not when this tool should be selected over clawbridge_status or clawbridge_events.

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