Skip to main content
Glama

Rule reply: template after 24 hours

dosai_set_rule_whatsapp_template
Destructive

Official WhatsApp: what an event rule's "reply with text" sends to a client silent over 24h, where text cannot go: "reengage" (paid «bring back» template), an automation_templates id from dosai_get_whatsapp_template_settings, or "none". Paid, in the daily cap: ask the owner. Editor+.

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>",
      "rule_id": "<rule_id>",
      "choice": "<choice>"
    },
    "name": "dosai_set_rule_whatsapp_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYes
rule_idYesRule id from dosai_list_rules.
project_idYesFrom dosai_list_projects.

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 declare write/destructive behavior, and the description adds real context beyond them: the change is billable ("Paid, in the daily cap: ask the owner") and requires Editor+ permission. It stops short of saying that an existing choice is overwritten when a new one is set, which matters given destructiveHint=true, but the cost and authorization disclosures are substantive.

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?

Every clause carries information, but the single dense sentence stacks quoted fragments and parentheticals, making it harder to parse than a two-sentence split between "what it does" and "what values cost what." The leading "Official WhatsApp:" label is also a slightly awkward front-load.

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?

For a three-parameter setter with no output schema, the description covers purpose, valid values, billing impact, and permission level — enough to call it correctly. The only meaningful omission is what happens to the prior value and whether the tool returns the updated setting, which is minor against annotations already flagging destructive behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description compensates for the gap by explaining the "choice" parameter's accepted values: "reengage" is a paid "bring back" template, an automation_templates uuid must come from dosai_get_whatsapp_template_settings, or "none" disables it. This adds meaning the enum-free anyOf schema cannot express. rule_id and project_id rely on the schema's own descriptions, which are adequate.

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 states a specific verb and resource: it sets what an event rule's "reply with text" sends to a client who has been silent over 24h, where plain text is blocked. That is far more precise than the title alone, and it names dosai_get_whatsapp_template_settings as the source of valid ids, which separates it from sibling setters. The compressed grammar ("what an event rule's 'reply with text' sends") costs a little clarity, but the operation is unambiguous.

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 context is implied rather than stated: the 24h WhatsApp window explains why this setting exists, and "ask the owner" plus "Editor+" indicate prerequisites. However, it never says explicitly when to change this versus adjusting the daily template cap (dosai_set_whatsapp_template_cap) or editing the rule itself, so the agent must infer routing between siblings.

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