Skip to main content
Glama

Template sending limits

dosai_get_whatsapp_template_settings
Read-onlyIdempotent

Official WhatsApp number: marketing_daily_cap (paid MARKETING templates follow-ups and broadcasts may send per day), payment_ok (false = no card at Meta), reengage (is the «bring the conversation back» template ready), automation_templates (the owner's own templates a follow-up step or a rule can send after 24 hours: id, title, body, category, state; only state=approved can be chosen). official=false: not the official way.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered structurally. The description's added value is field-level semantics — e.g. payment_ok=false means no card at Meta, only state=approved templates are selectable — which is genuine context an agent would otherwise lack. It still says nothing about freshness, per-project scoping behavior, or what 'official' tracks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense run-on sentence organized as a field glossary rather than front-loaded with purpose. Individual clauses carry real information, but the parenthetical explanations, guillemets around «bring the conversation back», and the trailing 'official=false: not the official way' read as cryptic notes rather than structured guidance.

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

Completeness3/5

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

There is no output schema, so the description is the only place the response shape is explained — and it does cover four fields (marketing_daily_cap, payment_ok, reengage, automation_templates with id/title/body/category/state). It is roughly sufficient for a simple read tool, but leaves unclear what 'official' means and whether automation_templates arrives as a list, which matters for parsing.

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?

With a single parameter and 100% schema description coverage, the schema already explains project_id and points to dosai_list_projects. The description contributes nothing further about that parameter, which is acceptable at this coverage but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a verb or resource; it opens with 'Official WhatsApp number:' and drifts into a glossary of returned fields. An agent can infer it reads template sending limits/settings for a project, but that inference comes from the title and field names, not from the text itself. It is distinguishable in practice because no sibling describes these same fields, but that is incidental.

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?

There is no statement of when to call this versus dosai_list_whatsapp_templates, dosai_set_whatsapp_template_cap, or dosai_get_whatsapp_status. Implicitly it reads caps before sending a marketing template or configuring an automation step, but that workflow is never spelled out. No exclusions or prerequisites are given.

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