Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get the guests' answers to a calendar event

get_message_responses
Read-onlyIdempotent

See how the guests answered a WhatsApp calendar event: going, not going or maybe.

Only works on a calendar event; any other message answers invalid_request: message_not_calendar.

The answer has counts (how many guests are going, not going or maybe, and how many extra guests those who are going or maybe are bringing) and responses, one entry per guest with who they are, their answer, any extra guests they bring and when they answered. A guest who changes their mind leaves one entry showing the latest answer, so this is a current snapshot and not a history. To be told as answers come in, watch for message.calendar_responded with list_events.

An event nobody has answered yet returns zero counts and an empty list, which is the normal answer and not an error.

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

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses failure behavior on non-calendar messages, the snapshot-not-history semantics (a guest who changes their mind leaves one entry), and that empty results are normal rather than an error. It stops short of covering auth or rate-limit behavior, but the important edge cases are all here.

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?

The purpose sentence is front-loaded, and the follow-up paragraphs are broken by concern (errors, return shape, empty state). It is slightly long, and the return-shape paragraph partly duplicates what the output schema already conveys.

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?

Given an output schema exists, the description still usefully frames what `counts` and `responses` mean semantically, adds the current-snapshot caveat that the schema cannot express, and resolves the empty-result ambiguity. Nothing an agent needs to call or interpret it is missing.

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 both `message_id` and `number_alias` are already documented in the schema. The description adds nothing about parameter formatting or defaults beyond that, so this sits at the baseline.

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 ('See how the guests answered a WhatsApp calendar event') plus the exact enumerable answer set. It is immediately distinguishable from siblings like get_message_reactions or get_message_receipts, which cover different message types.

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?

Explicitly scopes applicability ('Only works on a calendar event') and names the exact error users get otherwise, including the error code. It also routes the agent to an alternative mode of working, telling it to watch `message.calendar_responded` via `list_events` when it needs live updates rather than a snapshot.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.