Convertway WhatsApp MCP Server

get_whatsapp_templates

List WhatsApp message templates grouped by module. Optionally filter by module name to find specific templates.

Instructions

List available WhatsApp message templates grouped by module

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_whatsapp_templates"
  }
}

Input Schema

Name	Required	Description	Default
`module`	No	Filter templates by module name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavioral traits. It only states the basic action, omitting any mention of permissions, rate limits, pagination, or whether it includes only approved templates. This leaves the agent with insufficient information for safe invocation.

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 description is a single concise sentence with no redundant information. It is front-loaded with the core action. However, it could benefit from slightly more structure to note the grouping behavior explicitly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain the return format of the grouped templates. It only says 'grouped by module' without details on the grouping structure, list size, or any nested data. This incompleteness impairs the agent's understanding of the tool's output.

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 100% with a clear description for the single parameter. The description adds context about grouping by module but does not clarify filter behavior (e.g., exact match or substring). Since the schema already covers the parameter well, the baseline of 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 clearly states the tool lists WhatsApp templates grouped by module, which is a specific verb-resource combination. However, it does not differentiate this tool from sibling tools like list_templates_by_module or list_all_templates, which also list templates.

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?

No guidance is provided on when to use this tool versus alternatives. With multiple sibling tools for listing templates, the description should explain when grouping is preferable or when to use filtering vs full listing.

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

Deploy Server