Skip to main content
Glama

Verify a phone code

verify_code

Verify the 6-digit code sent by request_verification_code. On success, returns a session_token, pass this exact string as session_token to list_my_rides, get_ride_status, cancel_ride, and redeem_gift. The token expires after 24 hours.

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": {
      "phone": "<phone>",
      "code": "<code>"
    },
    "name": "verify_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
phoneYesMust match the phone passed to request_verification_code (any common format; non-digits other than a leading + are stripped server-side).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, and the description still adds real behavioral facts: the return value is a session_token, it must be passed verbatim, and it expires after 24 hours. It stops short of describing error behavior or retry/rate-limit characteristics for wrong codes.

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?

Three short sentences, each doing distinct work: what the tool does, what it returns and how to use it, and the expiry limit. The critical token-handling instruction is front-loaded in the second sentence with no filler.

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?

With no output schema, the description correctly carries the return-value burden by naming session_token and its 24-hour lifetime, and it explains cross-tool usage. The remaining gap is failure handling — no statement of what a rejected code returns or whether a new code must be requested — which matters for a verification tool.

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 50% — the phone parameter is already documented in the schema with format-stripping details, while code only carries length constraints. The description contributes the meaning 'the 6-digit code sent by request_verification_code', which links code to the issuing call, but adds no syntax or error semantics beyond that, so the 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 and resource ('Verify the 6-digit code') and ties it to the originating sibling request_verification_code, so the agent immediately knows this is the second step of an auth flow rather than an unrelated validation call. It also names the concrete artifact produced (session_token), which distinguishes it from every other sibling.

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?

The prerequisite is explicit ('sent by request_verification_code'), and the downstream usage is spelled out by listing the exact tools the resulting token unlocks. There are no explicit exclusions or failure-path guidance (e.g. what to do when the code is wrong or expired), which keeps it short of a 5.

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.

Resources