Skip to main content
Glama

Agree to a template's new price

dosai_confirm_whatsapp_template_price
Destructive

Meta moved a template to another category (owner_category ≠ category), usually to MARKETING, about three times dearer per message; until the owner agrees it is not sent. OWNER'S MONEY: name the new price, call only after a yes. Admin or owner.

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>",
      "template_id": "<template_id>"
    },
    "name": "dosai_confirm_whatsapp_template_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses that this spends the owner's money, that the new price is usually ~3x per message, that the template remains unsent until agreement, and that the caller must be admin or owner. These are exactly the behavioral traits an agent needs before invoking a destructive, cost-incurring action.

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?

Front-loads the situation, then the cost warning, then the authorization rule. Dense but every clause carries weight. Minor deduction because 'name the new price' is slightly cryptic about who should be told, and the ALL-CAPS emphasis is informal.

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 destructive, money-affecting write with no output schema, it covers rationale, precondition, authorization, and consequence (unsent until agreed). It could say a bit more about what the confirmation actually changes or whether it can be undone, but overall it is sufficiently complete to call safely.

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

Parameters2/5

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

Schema coverage is only 50%: project_id is described ('From dosai_list_projects') but template_id has no schema description. The prose adds no meaning about either parameter—it never says what template_id refers to or how to obtain it—so it fails to compensate for the coverage gap.

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 verb (confirm/agree) and resource (WhatsApp template price) and explains the triggering situation (Meta re-categorized the template to a dearer category). Clear enough to distinguish from edit/delete siblings, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a strong precondition: 'call only after a yes' from the owner, plus the fact that the template is not sent until agreement. That tells the agent when to call, but it never names an alternative tool or explicitly says when not to call (e.g., before re-checking the quote).

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