Skip to main content
Glama
Sign In
bale-mcp

bale-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Bot: wait for reply

bot_wait_for_reply

Blocks until a user sends a message or presses a button, then returns new messages marked as read. Use after sending a message; if nobody replies, it times out and you can call again.

Instructions

Wait until someone writes in a chat or presses a button, then return the new messages (marked read).

Use after bot_send_message. Returns timed_out=true and no messages if nobody answered; call again to keep waiting.

Input Schema

NameRequiredDescriptionDefault
chat_idYesNumeric chat id (see bot_list_chats).
timeout_secondsNoHow long to wait; use less if your client cancels long calls.
after_message_idNoOnly messages newer than this id: pass the message_id you sent; a button press on it counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.2.0
    • changedInput schema / properties / after_message_id / description
      Previous value: -"Only messages newer than this one. Pass the message_id of the question you sent; a button press on it counts."New value: +"Only messages newer than this id: pass the message_id you sent; a button press on it counts."
    • removedInput schema / properties / after_message_id / title
      Removed value: -"After Message Id"
    • changedInput schema / properties / chat_id / description
      Previous value: -"Numeric chat id (from bot_get_new_messages or bot_list_chats)."New value: +"Numeric chat id (see bot_list_chats)."
    • removedInput schema / properties / chat_id / title
      Removed value: -"Chat Id"
    • changedInput schema / properties / timeout_seconds / description
      Previous value: -"How long to wait. Use a shorter wait if your MCP client cancels long tool calls."New value: +"How long to wait; use less if your client cancels long calls."
    • removedInput schema / properties / timeout_seconds / title
      Removed value: -"Timeout Seconds"
    • removedInput schema / title
      Removed value: -"bot_wait_for_replyArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "bot_wait_for_replyDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already signal readOnlyHint=false and idempotentHint=false, but the description adds the reason: returned messages are "marked read," a side effect an agent must know about. It also discloses the timeout contract (timed_out=true, no messages), which annotations alone do not convey. No contradiction with the non-read-only, non-idempotent hints.

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 tight sentences: the first defines the action and side effect, the second gives the call-site and retry rule. No filler and the core behavior is front-loaded.

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?

With no output schema, the description carries the return-value burden and does so partially: it explains the timeout case but not the shape of the returned messages. For a blocking tool with rich annotations and full param coverage, this is nearly complete but not exhaustive.

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%, so chat_id, timeout_seconds, and after_message_id are fully documented in the schema. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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: it waits for chat activity (message or button press) and returns new messages. The blocking/waiting nature clearly separates it from polling-style siblings like bot_get_new_messages, though it never names that sibling explicitly.

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?

"Use after bot_send_message" gives a concrete trigger, and "call again to keep waiting" defines the retry loop for the timeout case. It stops short of saying when to prefer this over bot_get_new_messages or bot_read_chat.

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