Skip to main content
Glama

Daily cap of paid templates

dosai_set_whatsapp_template_cap
Destructive

Set how many paid MARKETING templates a day follow-ups and broadcasts may send from the official number. It is the owner's daily spend at Meta: say it in money, change only on the owner's word. 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>",
      "marketing_daily_cap": "<marketing_daily_cap>"
    },
    "name": "dosai_set_whatsapp_template_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
marketing_daily_capYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context: this governs real spend at Meta, it throttles follow-ups and broadcasts, and it requires admin or owner privileges. It stops short of 5 because it doesn't say what happens to sends already queued or whether a lowered cap takes effect immediately.

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 tight sentences, with the resource and blast radius front-loaded and the authorization note last. The only wasted/confusing phrase is "say it in money," which muddies an otherwise efficient definition.

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?

For a destructive, no-output-schema mutation with an under-documented required parameter, the description covers purpose, scope, and permission well. It omits the effect of lowering the cap relative to current usage and what confirmation the caller receives, leaving a gap an agent would want filled.

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 50%: project_id is documented in the schema, and the description supplies the meaning for the undocumented marketing_daily_cap (paid marketing templates per day, from the official number). However, "say it in money" conflicts with an integer 1-1000 template count, introducing ambiguity about the unit rather than resolving it.

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 and resource: it sets the daily cap on paid MARKETING templates sent by follow-ups and broadcasts from the official number. That is far more precise than the tool name alone. It doesn't explicitly contrast itself with the nearby sibling dosai_set_rule_whatsapp_template, so it stops short of 5.

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?

"change only on the owner's word. Admin or owner." gives a real authorization/usage constraint, and "the owner's daily spend at Meta" frames the context for changing it. There is no explicit when-not guidance and no named alternative for related settings.

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