Skip to main content
Glama

add_test_recipient

Starts verifying a phone number or email as a test recipient by sending a 6-digit code, so confirmed test messages actually arrive instead of only being logged in the sandbox.

Instructions

Start confirming a phone number or email as a test recipient. A 6-digit code is sent to it. Once confirmed, test messages to that recipient really arrive (otherwise test mode only logs them in a sandbox). Only add numbers or emails that belong to the account owner. Test key (sk_test_) only. After calling this, ask the human for the 6-digit code they received and call confirm_test_recipient.

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": {
      "to": "<to>"
    },
    "name": "add_test_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesIsraeli mobile number in E.164 format +9725XXXXXXXX (05XXXXXXXX is also accepted), or an email address for the email channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the outbound side effect (a code is sent), the consequence of confirming (real delivery vs. sandbox logging), the key-type restriction, and the human-in-the-loop step. It does not say what state an unconfirmed recipient stays in, whether codes expire, or whether calls are rate-limited, which keeps it below a 5.

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?

Five short sentences, front-loaded with what happens, then the payoff of confirming, then constraints, then the required next call. Every sentence carries either a constraint or an operational consequence; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no annotations and no output schema, the description supplies the flow, the side effect, the approval requirement, the key restriction, and the next step. An agent has everything needed to invoke it correctly and to route to confirm_test_recipient afterward.

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

Parameters5/5

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

Schema coverage is already 100% for the single 'to' parameter, so the format details are redundant, but the description adds real meaning the schema lacks: the value must belong to the account owner, and it clarifies that this parameter selects between the SMS and email channel. That constrains value selection rather than restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start confirming a phone number or email as a test recipient') plus the immediate effect ('A 6-digit code is sent to it'). The two-step nature is made explicit by naming confirm_test_recipient, so an agent can separate this from the confirmation sibling without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete when-to-use context (test-mode recipients), explicit constraints (only account-owner numbers/emails, sk_test_ keys only), and a named follow-up action with the exact next call. Nothing is left to inference about the ordering of add vs. confirm.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.