Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_claude_callback_ack

Acknowledge a callback batch from a verified Claude manager session using its batch_id and lease_id, so the manager can confirm receipt and continue processing.

Instructions

WRITE: acknowledge one exact callback batch returned to this same verified Claude manager session.

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": {
      "batch_id": "<batch_id>",
      "lease_id": "<lease_id>"
    },
    "name": "aiworkhub_claude_callback_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesbatch_id of the callback_ready reply being acknowledged.
lease_idYeslease_id from that same callback_ready reply.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / batch_id / description
      Added value: +"batch_id of the callback_ready reply being acknowledged."
    • addedInput schema / properties / lease_id / description
      Added value: +"lease_id from that same callback_ready reply."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds scoping context ('this same verified Claude manager session') but does not disclose idempotency, whether acknowledgment consumes the batch, or what state changes result. Consistent with annotations, not contradictory.

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, and the WRITE prefix immediately signals the operation type. It is terse but efficient; the only minor cost is that terseness borders on under-specification.

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?

An output schema exists, so return values need not be explained, and both parameters are fully documented in the schema. The description still omits how this relates to the callback_wait sibling and whether acknowledgment is idempotent, leaving a modest gap for a write tool.

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 100%, and the schema already explains that batch_id and lease_id come from the callback_ready reply. The description adds only the notion of 'one exact callback batch' and does not enhance parameter meaning beyond the schema.

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 ('acknowledge') and resource ('one exact callback batch'), which clearly distinguishes it from a wait/read tool. It does not explicitly name or contrast with the sibling aiworkhub_claude_callback_wait, so it falls short of full sibling differentiation.

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?

The phrase 'returned to this same verified Claude manager session' implies the precondition that the batch must originate from the current session, and the schema descriptions reinforce that it follows a callback_ready reply. However, there is no explicit when-to-use vs when-not guidance or direct routing to callback_wait.

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

Deploy Server

Other Tools