Skip to main content
Glama

clawbridge_events

Read durable Luban task event notifications from a local outbox to monitor task status summaries, optionally limiting results to pending events.

Instructions

Read durable Luban task events. Events form a local notification outbox and contain only a short status summary.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
pendingOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 burden. It does add real value by disclosing that events are durable, local, and limited to a short status summary (a data-fidelity warning). It says nothing about ordering, whether reading affects pending state, or that the operation is non-destructive.

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 front-loaded sentences with no filler. Slight under-specification rather than verbosity, and the second sentence is the more useful of the two yet arrives last.

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 simple two-parameter read with no annotations and no output schema, the description covers what the resource is but not how to read it: no pagination/limit guidance, no meaning for pendingOnly, and no hint of the returned event fields beyond "short status summary."

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 neither of the two parameters is mentioned in the description. In particular, pendingOnly defaults to true, so an agent could easily believe it is seeing all events; the description never explains that filter or the limit default of 20.

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 durable Luban task events") and characterizes the resource as "a local notification outbox," which separates it from sibling reads like clawbridge_tasks and clawbridge_logs. It stops short of naming which sibling to use for the alternative case.

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 the closest siblings (clawbridge_acknowledge_event, clawbridge_logs, clawbridge_tasks). The outbox framing implies a polling/notification use case, but the agent must infer it.

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