Skip to main content
Glama

Whether somebody is already on the do-not-contact list

dnd_check
Read-onlyIdempotent

Check whether a phone number is suppressed on a channel before contacting it. Returns whether it is blocked and why. Read only.

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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesWhich channel to check
phoneNumberYesInternational format, e.g. +919999999999

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the trailing 'Read only.' adds nothing. The useful addition is that the call returns a blocked flag plus the reason, which is real behavioral context absent from the annotations. Scope is per-channel, which is also informative.

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?

Three short sentences, purpose front-loaded, return value second. The only waste is 'Read only.', which merely restates the readOnlyHint annotation.

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 two-parameter lookup with full schema coverage and rich annotations, the description supplies the missing piece: what the result means (blocked plus reason). A brief note on what a non-suppressed response looks like would close the remaining gap.

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% with an enum on channel and a format example on phoneNumber, so the schema carries parameter meaning. The description only loosely reinforces that suppression is evaluated per channel and per number, adding little beyond structured fields.

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: check whether a phone number is suppressed on a given channel, plus what it returns. The verb 'check' contrasts cleanly with the mutation sibling dnd_add, though that sibling is never named.

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?

'before contacting it' implies the pre-contact gating use case, so the when-to-use is inferable. There is no explicit exclusion or named alternative (e.g. dnd_add for adding a suppression), so guidance stops at implication.

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.