Skip to main content
Glama

Templates for one dialog

dosai_list_chat_templates
Read-onlyIdempotent

For a dialog on the official WhatsApp number: approved templates that can be sent now, their variables, and prefill (client's name, topic of the dialog) to fill them. opted_out=true: the client said stop, only UTILITY ones go. 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>"
    },
    "name": "dosai_list_chat_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
conversation_idYesFrom dosai_list_conversations.

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 cover the read-only, idempotent, non-destructive profile, yet the description still adds real behavioral context: only approved templates are returned, only those currently sendable, and the opted_out case narrows results to UTILITY templates. It also discloses the permission floor ('Editor or above'), which the annotations do not.

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 dense sentences, front-loaded with the resource and its scope, then the access rule. Nothing is padding, though the telegraphic phrasing ('opted_out=true: the client said stop') takes a moment to parse.

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 still conveys what comes back (templates, their variables, prefill for client name and dialog topic) and what governs inclusion (approval status, opted-out filtering, permission level). Only the boundary against the other template-listing tools is left implicit.

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 both UUID parameters already document their source tools, so the schema carries the parameter burden. The description adds no argument-level meaning, and its reference to 'opted_out=true' points at something that is not a parameter of this schema, which risks momentary confusion.

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?

States a specific resource (approved WhatsApp templates for one dialog) and what the response carries (variables and prefill values). The scope qualifier 'for a dialog' separates it from the account-wide template listing siblings, though it does not name those siblings explicitly.

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 'approved templates that can be sent now' implies the tool is for picking a sendable template during a conversation, and 'Editor or above' states the access prerequisite. There is no explicit when-not guidance or named alternative such as the general WhatsApp template listing, so the agent must infer the boundary.

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