Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_claude_callback_wait

Read-only

Blocks until a callback arrives for a verified Claude Code manager session, claiming the next batch while acknowledging the previous one to prevent retried or lost leases.

Instructions

BLOCKING READ/CLAIM: wait for a callback for this verified Claude Code manager session. Acknowledge the previous batch by passing its batch_id/lease_id as ack_batch_id/ack_lease_id here, or call aiworkhub_claude_callback_ack; an unacknowledged lease is retried, never lost.

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": "aiworkhub_claude_callback_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
ack_batch_idNobatch_id from the previous callback_ready reply, acknowledged while the next batch is claimed; leave empty on the first wait.
ack_lease_idNolease_id from that same callback_ready reply; pass it together with ack_batch_id.
timeout_secondsNoSeconds to wait for a callback; default 240, clamped to a server maximum (at least 1) that the reply reports.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.67
    • addedInput schema / properties / ack_batch_id / description
      Added value: +"batch_id from the previous callback_ready reply, acknowledged while the next batch is claimed; leave empty on the first wait."
    • addedInput schema / properties / ack_lease_id / description
      Added value: +"lease_id from that same callback_ready reply; pass it together with ack_batch_id."
    • addedInput schema / properties / timeout_seconds / description
      Added value: +"Seconds to wait for a callback; default 240, clamped to a server maximum (at least 1) that the reply reports."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

It discloses key behavior beyond the annotations: the call is BLOCKING, it claims a lease, unacknowledged leases are retried and never lost, and acknowledgement can be performed in this call or via the ack tool. These are important operational traits for an agent deciding whether to block.

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?

The description is front-loaded with the blocking/wait purpose, then immediately explains acknowledgement and retry behavior. It is dense with useful information and has no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, annotations, and full schema coverage, the description covers the critical blocking and lease-acknowledgement context. It does not describe timeout or return shape, but those are handled by the schema and output schema.

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 coverage is 100%, so the parameters are already well documented. The description reinforces that ack_batch_id/ack_lease_id come from the previous callback_ready reply and are used while claiming the next batch, but it does not add much beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: wait for a callback for a verified Claude Code manager session. It distinguishes the tool from its ack sibling by naming aiworkhub_claude_callback_ack and explaining that acknowledgement can happen either here or there.

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?

It clearly states the acknowledgement workflow and names the alternative tool, but does not give an explicit 'use this instead of' exclusion or prerequisite beyond the verified session context. The guidance is strong but not fully exhaustive.

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