Skip to main content
Glama

confirm_test_recipient

Verifies a test recipient by submitting the 6-digit code the human received, so send_test_otp deliveries actually reach that number or email.

Instructions

Finish confirming a test recipient with the 6-digit code the human received after add_test_recipient. On success, send_test_otp to this recipient is really delivered.

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>",
      "code": "<code>"
    },
    "name": "confirm_test_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe same number or email passed to add_test_recipient.
codeYesThe 6-digit code the human received.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the flow context and the effect that the recipient becomes genuinely deliverable, but does not cover failure behavior (invalid/expired code), whether the call is idempotent, what state changes on the recipient, or any limits on attempts.

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 short sentences with the action and prerequisite front-loaded and zero filler. The second sentence's slightly informal wording ('is really delivered') still conveys a meaningful outcome in few words.

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-required-parameter confirmation tool with no output schema, the description covers purpose, prerequisite, and success effect, which is most of what an agent needs. The main omission is error handling for an incorrect or expired code.

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 description coverage is 100%, so both parameters are already documented in structured form, and the description largely mirrors that ('the 6-digit code the human received', 'the same number or email'). It adds only the linkage back to add_test_recipient, which is a marginal gain beyond 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?

The description names a specific verb ('Finish confirming') and resource ('a test recipient'), and ties it to a concrete artifact (the 6-digit code). It implicitly distinguishes itself from add_test_recipient by naming it as the preceding step, so an agent can tell which tool starts the flow and which completes it.

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?

It clearly states the precondition — this is used after add_test_recipient, once the human has received the code — and describes the payoff (send_test_otp becomes really delivered). It does not explicitly say what to do if the code is wrong or expired, nor does it exclude any alternatives beyond the implied ordering.

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