Skip to main content
Glama

Write to a client by template

dosai_send_whatsapp_template
Destructive

Send an approved template into a dialog on the official WhatsApp number: the way to write when the client is silent over 24 hours (Meta refuses a plain message then). A REAL PERSON GETS IT, IT CANNOT BE UNSENT AND META CHARGES THE OWNER: show the owner the final text, send only after a yes. values fills every variable by name (dosai_list_chat_templates). Editor or above.

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>",
      "conversation_id": "<conversation_id>",
      "template_id": "<template_id>"
    },
    "name": "dosai_send_whatsapp_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesNoVariable name → text.
project_idYesFrom dosai_list_projects.
template_idYes
conversation_idYesFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so irreversibility and external reach are partly covered. The description still adds genuinely new context: a real person receives it, Meta bills the owner, and the caller needs Editor role or above — though it says nothing about the response or failure modes.

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 purpose first, then condition, then consequence, then params and permission — a logical order with no filler sentences. The all-caps warning block is deliberate emphasis rather than waste, though it slightly disrupts the otherwise tight prose.

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 destructive, open-world send with no output schema, the definition covers the risk, mandatory confirmation, required role, and parameter sourcing. It omits what a successful send returns and how an unapproved or mismatched template is handled.

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 75%, and the description compensates for the gap by explaining that 'values' fills every variable by name and pointing to dosai_list_chat_templates as the source of template ids. That adds real meaning beyond the schema's 'Variable name → text.' boilerplate.

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?

Names a specific verb (send) and resource (approved template) into a dialog on the official WhatsApp number, and immediately scopes it against plain messages ('Meta refuses a plain message then'). An agent can tell it apart from the messaging siblings without opening a schema.

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?

Gives an explicit trigger condition — the client has been silent over 24 hours so Meta blocks a plain message — plus a hard precondition ('show the owner the final text, send only after a yes'). It does not name the sibling to use for the ordinary in-window case, so the alternative is only implied.

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