Skip to main content
Glama

verify_otp

Checks a one-time code sent to a phone number or email, returning valid true/false and a failure reason such as wrong_code, expired_or_missing, or too_many_attempts.

Instructions

Check a one-time code that was sent with send_test_otp (or the live API) for a phone number or email. Returns valid true/false and, when false, the reason (wrong_code, expired_or_missing, too_many_attempts).

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": "verify_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe same recipient the code was sent to.
codeYesThe code entered by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 meaningful work: it discloses the return shape (valid true/false) and enumerates the three failure reasons (wrong_code, expired_or_missing, too_many_attempts), implying attempt limits and code expiry. It does not state rate limits, attempt-counting rules, or whether the code is consumed on success, which keeps it short of 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?

Two sentences, front-loaded with the purpose, followed by the return contract. Every clause carries information; nothing is redundant or padded.

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 verification tool with no output schema, the description supplies the return contract and failure taxonomy that would otherwise be invisible, and the schema fully covers inputs. Remaining gaps are secondary behavioral details such as attempt counting and whether a successful verification invalidates the 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 coverage is 100%, so both parameters are already documented ('the same recipient the code was sent to' and 'the code entered by the user'). The description repeats the recipient linkage but adds no format, normalization, or validation detail beyond the schema, so baseline 3 applies.

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 (check/verify) and resource (one-time code) and explicitly ties it to the sibling that produces the code (send_test_otp), so an agent can distinguish verification from sending without opening either 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?

Clearly frames the usage context: it is the verification step for a code delivered by send_test_otp or the live API, and it works for phone numbers or email. It gives no explicit when-not guidance or mention of adjacent siblings like check_delivery_status, so it is clear context rather than full routing guidance.

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