Skip to main content
Glama

Request a phone verification code

request_verification_code

Send a 6-digit SMS code to a phone number, to verify the caller owns it before showing ride history or allowing a cancellation. Required before calling list_my_rides, get_ride_status, cancel_ride, or redeem_gift.

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

Input Schema

NameRequiredDescriptionDefault
phoneYesAny common format is fine (e.g. "305-555-0100"); non-digit characters 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 disclose a non-read-only, non-idempotent, open-world (external SMS) operation, so the bar is lower; the description adds the delivery channel, the 6-digit shape, and the authorization gating it enforces. It does not cover code expiry, resend/rate-limit behavior, or what happens on repeated requests despite idempotentHint=false.

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?

One sentence, zero waste, with the mechanism ('6-digit SMS') front-loaded and the prerequisites trailing. Nothing is redundant with the title or schema.

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 one-parameter, non-destructive tool with full annotation coverage and no output schema, the description covers the essentials. The missing piece is the handoff to verify_code and any note about code lifetime, which an agent needs to avoid a stranded flow.

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?

With a single parameter and 100% schema description coverage, the schema already documents accepted formats and server-side digit stripping. The description says only 'to a phone number' and adds no meaning about the parameter beyond that, 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 and resource ('Send a 6-digit SMS code to a phone number') plus the outcome it enables ('verify the caller owns it'). This clearly separates it from verify_code, which is the follow-on step, and from the gated read/cancel tools.

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?

Explicitly names the four tools that require this call first (list_my_rides, get_ride_status, cancel_ride, redeem_gift) and gives the intent behind it. The notable gap is that it never mentions verify_code, even though the sibling exists and is the obvious next step after receiving the SMS.

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