Skip to main content
Glama

Official WhatsApp templates

dosai_list_whatsapp_templates
Read-onlyIdempotent

Templates of the official WhatsApp number: the only way to write first or after 24 hours of silence. Each: id, purpose, language, category (MARKETING costs more than UTILITY, Meta decides), status at Meta (only APPROVED is sent), rejected_reason, body with {{1}}…{{n}} and variables (what each number means). owner_category ≠ category: Meta changed the price, the owner agrees in the cabinet before it goes again. meta_synced=false: statuses are from the last check. 409 = no official number.

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_list_whatsapp_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already flag readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: category cost implications with Meta making the pricing call, that only APPROVED templates can be sent, what rejected_reason and statuses mean, the owner_category vs category discrepancy, and that meta_synced=false means statuses are stale. It also documents the 409 error meaning (no official number), which is exactly the kind of operational detail annotations cannot convey.

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 what the tool returns and packs a lot into a short space with no filler sentences. The telegraphic style and the mid-stream digression on pricing (owner_category ≠ category) make it slightly dense to parse, but every clause carries actionable information.

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?

With no output schema, the description fully compensates by enumerating returned fields, explaining variable placeholders in the body, and covering the primary failure mode (409). For a one-parameter read tool this leaves nothing an agent needs 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?

There is a single project_id parameter with 100% schema coverage and an inline pointer to dosai_list_projects, so the schema already does the work. The description adds nothing about project_id semantics; baseline 3 is appropriate.

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 names the resource precisely (templates of the official WhatsApp number) and enumerates the fields each record carries, which makes it clearly a read/list operation. It does not explicitly name sibling listing tools such as dosai_list_chat_templates or dosai_get_whatsapp_template_settings, so differentiation relies on the 'official WhatsApp number' qualifier rather than a direct contrast.

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 phrase 'the only way to write first or after 24 hours of silence' explains why templates matter, implying you fetch this list before sending via dosai_send_whatsapp_template. However, there is no explicit when-to-use/when-not guidance and no pointer to the create/edit/delete or settings siblings, so routing is left to inference.

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