Skip to main content
Glama

clawbridge_acknowledge_event

Acknowledge delivery of a local task event after it is shown to the user or sent by a configured notifier, confirming the event has been handled.

Instructions

Acknowledge delivery of a local task event after it has been shown to the user or delivered by a configured notifier.

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": {
      "eventId": "<eventId>"
    },
    "name": "clawbridge_acknowledge_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 never says what acknowledging actually does — whether the event is marked consumed, removed from the queue, or merely flagged; nor whether the call is idempotent, what happens for an already-acknowledged or unknown event, or whether permissions are required. For an unannotated mutation this is a substantial gap.

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?

A single front-loaded sentence with no filler; the purpose and the precondition arrive immediately. The trailing clause is dense but each part adds usable information.

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?

For an unannotated, no-output-schema mutation, the definition should explain the effect of the call and the shape of the result. Neither is present, and the single parameter is undocumented, leaving the agent unable to predict consequences of a wrong or repeated call.

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 coverage is 0% and the description never mentions the sole parameter eventId — not its UUID format, not where to obtain a valid ID (presumably from clawbridge_events or clawbridge_tasks). The phrase 'a local task event' only loosely gestures at the parameter.

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 — 'Acknowledge delivery of a local task event' — plus the triggering condition. It does not differentiate itself from siblings such as clawbridge_verify_delivery or clawbridge_events, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear precondition for when to call: only after the event 'has been shown to the user or delivered by a configured notifier.' No exclusions or named alternatives are offered, but the timing rule is explicit enough to guide invocation.

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