Skip to main content
Glama

list_test_recipients

Lists confirmed and pending test recipients plus remaining free test SMS, so you can verify a number will receive messages before sending a test OTP.

Instructions

List the confirmed and pending test recipients of this account and how many of the 5 free test SMS are left. Call it before send_test_otp to know whether a number will really receive messages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_test_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does disclose the meaningful behaviors: it is a read ('List'), it reports both confirmed and pending recipients, and it exposes the remaining free-test-SMS quota. It does not state whether the call is idempotent, whether it requires auth, or how the quota resets, so the safety profile is only implied.

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: the first states what is returned, and the second front-loads the call-ordering advice. Every clause earns its place, and there is no restatement of the tool name.

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?

No output schema exists, so the description has to explain return contents, and it does: recipient status categories plus remaining quota. For a no-parameter read tool, that is everything an agent needs in order to call it correctly and interpret the result.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline applies. The description correctly implies the listing is scoped to 'this account' rather than being a global enumeration.

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 plus the scope of what is returned: confirmed and pending test recipients of this account, along with the remaining count of the 5 free test SMS. That is enough for an agent to distinguish it from add_test_recipient, confirm_test_recipient, and check_delivery_status without opening any schema.

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

Usage Guidelines4/5

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

Gives explicit sequencing guidance, 'Call it before send_test_otp', and names the condition that makes it necessary: knowing whether a number will really receive messages. It does not cover what to do when the quota is exhausted or how this relates to the recipient-management siblings, so it is short of a full when/when-not specification.

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