Skip to main content
Glama

Set the ready questions in WhatsApp

dosai_set_whatsapp_ice_breakers
Destructive

Replace the official WhatsApp question buttons: up to 4, up to 80 characters, no emoji; [] removes them. A tap reaches the bot as a normal message. Confirm the wording with the owner. Admin or owner.

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>",
      "prompts": "<prompts>"
    },
    "name": "dosai_set_whatsapp_ice_breakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptsYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description goes further: it discloses the 4-item/80-character limits, the emoji prohibition, that an empty list removes the buttons entirely, and that taps arrive at the bot as ordinary messages. Those are genuine behavioral facts an agent cannot get from the annotations. It stops short of saying whether the old set is recovered or what partial failure looks like.

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?

Front-loaded with the action and its constraints, then side effects, then permissions — a sensible ordering with no filler sentences. The telegraphic fragments ("[] removes them", "Admin or owner.") are terse to the point of being slightly clipped, but nothing is wasted.

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?

For a two-parameter mutation with no output schema, the definition covers constraints, side effects, permissions, and a confirmation step, which is close to sufficient. The remaining gap is what a caller should expect on partial or rejected writes, which matters given destructiveHint=true.

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 coverage is 50%: project_id carries its own sourcing hint and prompts already encodes maxLength 80 and maxItems 4. The description restates both limits rather than adding new information about them, though "no emoji" and "[] removes them" are semantics absent from the schema. Net effect is roughly parity with the schema rather than a clear improvement.

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?

A specific verb ("Replace") plus a precise resource ("official WhatsApp question buttons") tells the agent exactly what changes. It is distinguishable from the read counterpart dosai_get_whatsapp_ice_breakers by the verb alone, though it never names that sibling as the way to inspect current values.

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 description supplies real preconditions — "Confirm the wording with the owner" and "Admin or owner" — which shape when the call is appropriate. However, it never states when to use this versus the getter, nor what the required role gate means operationally if the caller lacks it.

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