Skip to main content
Glama

workbuddy_wait_for_reply

Waits briefly for new WorkBuddy replies after you send a message; an empty list means the timeout elapsed, so you can poll again.

Instructions

Wait briefly for messages produced after a previously sent WorkBuddy message. An empty list means the timeout elapsed and the caller may poll again.

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": {
      "messageId": "<messageId>"
    },
    "name": "workbuddy_wait_for_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes
timeoutSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real behavior: this blocks briefly, and an empty list means timeout rather than no messages existing. It omits the maximum wait ceiling (the schema caps timeoutSeconds at 55) and says nothing about what non-empty results contain or whether repeated polling loses messages.

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?

Two sentences, no filler, with the wait semantics front-loaded and the return-value interpretation immediately after. Every clause carries information.

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 two-parameter polling tool with no output schema, the description usefully explains the empty-list return case, which is the main ambiguity. It still leaves the arguments and the shape of non-empty results undocumented, which matters at 0% schema coverage.

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%, so the description must compensate for both parameters and largely does not. It never explains that messageId identifies the previously sent message being followed, nor ties the word "timeout" to the timeoutSeconds parameter or its 55-second ceiling.

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?

The description names a specific verb and resource ("wait for messages") and scopes it to messages produced after a previously sent message, which separates it from a general history reader like workbuddy_message_history. It never explicitly names a sibling or alternative, so it stops short of a 5.

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 closing clause "the caller may poll again" implies the intended polling loop, which is useful contextual guidance. However, it never says when to prefer this over workbuddy_message_history or when not to call it (e.g., first-time retrieval of past messages).

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