Skip to main content
Glama

Get one WhatsApp template

template_detail
Read-onlyIdempotent

One template in full: its body text with {{1}}-style variables, header, footer, buttons, approval status and any rejection reason. Takes a template id. Read only.

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": {
      "templateId": "<templateId>"
    },
    "name": "template_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesThe template's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / templateId / description
      Previous value: -"The template_id from template_list"New value: +"The template's id"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety burden is covered; the description adds the genuinely useful disclosure of what is returned (body with {{1}} placeholders, header, footer, buttons, approval status, rejection reason). It does not say what happens for an unknown or deleted template id, which is the main remaining gap.

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?

Two short sentences, front-loaded with the payload description and ending with the id requirement. "Read only" is redundant against readOnlyHint=true, a small but real waste.

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 correctly carries the return-value burden by enumerating the fields returned. For a one-parameter read tool that is nearly sufficient; only error behavior for an invalid id is unaddressed.

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% and the single parameter is already documented, so "Takes a template id" adds no meaning beyond the schema. Baseline 3 applies when the schema does all the work.

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?

"One template in full" names the resource and makes the single-record scope unambiguous, which implicitly separates it from template_list. It never names the sibling explicitly, but an agent can tell this returns a detail record rather than a collection.

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?

Usage is only implied: needing a template's full contents rather than a listing. There is no explicit statement of when to prefer this over template_list or whatsapp_send_template, and no preconditions beyond supplying an id.

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.