Skip to main content
Glama

Record that somebody must not be contacted

dnd_add
Destructive

Adds a phone number to the organisation's do-not-contact list for one channel (VOICE, WHATSAPP or SMS), permanently. Each call records one entry; repeating it records a second entry.

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": {
      "phoneNumber": "<phoneNumber>",
      "channel": "<channel>"
    },
    "name": "dnd_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, validate and return the payload without writing
reasonNoWhy — e.g. 'asked to stop during call abc-1'. Recorded for audit
channelYesWhich channel to suppress. One entry per channel; call again for others
phoneNumberYesInternational format, e.g. +919999999999

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description adds substantive context beyond them: the effect is permanent and each call creates a new entry rather than deduplicating. It still doesn't say what happens if the number is already suppressed, but the mutation's permanence and non-idempotency are clearly disclosed.

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 sentences, both front-loaded, with the scope and channel set established before the duplicate-entry behavior. No filler or repetition.

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, non-idempotent mutation with no output schema, the description conveys the essentials: permanence, per-channel granularity, and duplicate behavior, while dryRun and reason are covered by the schema. Minor gaps (permission requirements, behavior when the number is already listed) keep it from a 5.

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 every parameter is already documented, including dryRun, reason, channel, and phone-number format. The description only restates that the channel is single-valued, so it meets the baseline without adding meaning beyond the schema.

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 ('adds') plus resource ('phone number to the organisation's do-not-contact list') plus scope ('one channel'), which is precise enough to distinguish it from dnd_check. It stops short of naming a sibling or explicitly contrasting with the check tool, so it isn't a 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?

Usage is implied by the description ('adds... permanently'), and the duplicate-entry sentence tells the agent how repeated calls behave, which is genuine usage-relevant guidance. There is no explicit when-to-use/when-not or pointer to dnd_check for verification-first workflows.

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.