Skip to main content
Glama

Disable Whatsapp Trigger

disable_whatsapp_trigger

Switch a WhatsApp trigger off: new records no longer send its message. It stays saved.

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": {
      "app_id": "<app_id>",
      "trigger_id": "<trigger_id>"
    },
    "name": "disable_whatsapp_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app the trigger belongs to.
trigger_idYesThe trigger id, from list_whatsapp_triggers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, it discloses the actual runtime consequence (no new records send messages) and that the trigger remains persisted, which corroborates destructiveHint=false in a meaningful way. It does not cover reversibility, whether in-flight messages are affected, or idempotentHint=false behavior on repeat calls.

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

Conciseness5/5

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

Two compact clauses, effect front-loaded, with no redundant restatement of the name or title. Every phrase carries information.

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 simple two-parameter toggle with a fully described schema and no output schema, the description covers purpose and outcome adequately. It could say what the call returns or how to re-enable, but nothing critical to correct invocation is missing.

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%, so both parameters are fully documented in the schema, and the description adds no additional meaning (no format, no source constraints). Baseline 3 applies since the schema does all the work.

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?

Specific verb ('Switch ... off') plus resource ('a WhatsApp trigger') and an explicit statement of the resulting effect ('new records no longer send its message'). 'It stays saved' implicitly distinguishes this from a delete, though it never names update_whatsapp_trigger as the re-enable path.

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 effect statement implies the when-to-use case (stop message sending without deleting), but there is no explicit guidance on when to use this versus update_whatsapp_trigger or how to reverse it. Usage is inferable rather than stated.

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