Skip to main content
Glama

Ready questions in WhatsApp

dosai_get_whatsapp_ice_breakers
Read-onlyIdempotent

Official WhatsApp: the up to 4 question buttons a person sees on first opening the chat (prompts); stats.prefilled = how many chats of 60 days began with one ad or link text (those people do not see them). suggest=true adds questions built from clients' real first messages, with a quote (editor+, 6 an hour).

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_get_whatsapp_ice_breakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
suggestNo
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already signal a safe, idempotent, closed-world read, and the description adds real context on top: suggest=true is gated to editor+ and rate-limited to 6 per hour, and regenerated questions include a quote drawn from real first messages. It also discloses a subtle behavioral caveat via stats.prefilled — chats that began with an ad or link text never saw the prompts — which an agent could not infer from the schema or annotations.

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?

It is front-loaded with the definition of the resource and every clause carries information (prompt definition, stats caveat, suggest behavior, tier, quota). The single run-on sentence with nested parentheses makes the transition between return-value semantics and parameter semantics harder to parse than necessary.

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 explain stats.prefilled, one non-obvious return field. It still does not describe the shape of the questions list itself or whether configured state (count, enabled flags) comes back, leaving a modest gap for a read tool with an undocumented output.

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 only 50%: project_id is documented in the schema, but suggest is bare there. The description compensates by explaining what suggest=true actually does — adds questions built from clients' real first messages — along with its permission tier and rate limit, which is meaning well beyond a boolean label.

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 defines the resource precisely — the up to 4 question buttons a person sees on first opening the chat (prompts) — so an agent knows exactly what object it is reading. It never states the action explicitly (no 'returns'/'retrieves'), relying on the tool name, and it does not differentiate itself from the sibling set_whatsapp_ice_breakers, which keeps it below 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this before deciding whether to configure ice breakers, and the obvious alternative (dosai_set_whatsapp_ice_breakers) is never mentioned. The only conditional, suggest=true, describes an option's effect rather than when the tool itself should be selected.

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.

Resources