Skip to main content
Glama

Check for a reply to an earlier ask / request_ack (non-blocking by default)

check_reply

Check whether a human replied to an earlier question or acknowledgment by message ID so you can resume after a timeout or cancelled blocking call. Returns response status and value.

Instructions

Look up whether the human has replied to a question or ack you sent earlier — use it to resume after ask/request_ack returned a timeout, or after your client cancelled the blocking call. Pass the message_id (and topic) you got back from that call. Returns immediately by default; set wait_seconds to briefly long-poll. Returns { responded, value?, replied_at? } — value is "yes"/"no" (a yes/no question), the chosen option (a multiple-choice question) or "ack". For an approval gate, only proceed when value === "yes". Replies are kept only ~30 minutes after the original message was sent.

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": {
      "message_id": "<message_id>"
    },
    "name": "check_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic the original message was sent to. Pass it explicitly when you passed one on the original call; otherwise it falls back to the same default (`.blipr-topic` file, then the BLIPR_TOPIC env var).
message_idYesThe message_id returned by a prior ask / request_ack call.
wait_secondsNoSeconds to long-poll for an answer (0 = instant check; default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.3
    • addedInput schema / properties / wait_seconds / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / topic / description
      Previous value: -"Topic the original message was sent to. Defaults to the BLIPR_TOPIC env var."New value: +"Topic the original message was sent to. Pass it explicitly when you passed one on the original call; otherwise it falls back to the same default (`.blipr-topic` file, then the BLIPR_TOPIC env var)."
  3. First observedv0.3.1

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses non-blocking default behavior, the optional long-poll via wait_seconds, the exact return shape { responded, value?, replied_at? }, and the ~30-minute reply retention window. It stops short of stating error behavior or what happens when message_id is unknown/expired, which keeps it from a 5.

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?

Front-loaded with the core purpose, then usage trigger, then parameters, then return contract and the retention caveat. Dense but every sentence carries actionable information with no filler.

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

Completeness5/5

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

No output schema exists, yet the description spells out the return object and the meaning of `value` across question types, plus the retention limit. For a 3-parameter read tool this is complete enough to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds value by linking message_id and topic to the prior ask/request_ack call and framing wait_seconds as a brief long-poll rather than a plain integer. It does not add syntax detail beyond the schema, so not a 5.

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?

States a specific verb and resource ('look up whether the human has replied to a question or ack you sent earlier') and explicitly ties it to the ask/request_ack siblings, so an agent can distinguish it from those tools without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions: use it after `ask`/`request_ack` returned a timeout or after the client cancelled the blocking call. It also states the approval-gate rule (proceed only when value === "yes"), leaving little to inference.

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