Skip to main content
Glama

Dial by Aloha Labs

wait_for_verification_code

Wait for a verification code (OTP) texted to one of your numbers and return it. Call this right after a site says it sent you a code. Each code is returned once.

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": {
      "api_key": "<api_key>",
      "number_id": "<number_id>"
    },
    "name": "wait_for_verification_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Dial API key (from sign_up)
serviceNoOnly accept codes from this sender, e.g. 'google'
number_idYesid from get_phone_number
timeout_secondsNoDefault 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 burden. It usefully discloses the consumptive semantics ('Each code is returned once'), warning the agent not to poll twice, but it never says the call blocks up to timeout_seconds, what happens if no code arrives within the window, or whether an error or empty result is returned — key for a waiting tool.

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, zero filler, with the purpose and the trigger condition front-loaded and the once-only caveat following. Nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must explain what comes back and how failure looks. It says the code is returned but not in what form, and says nothing about timeout/empty-result behavior or required auth beyond the schema's own api_key note.

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 api_key, number_id, service, and timeout_seconds are all documented in the schema. The description adds no format or behavioral nuance about filtering by sender ('service') or the 120-second cap, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Wait for a verification code (OTP)') plus the scope ('texted to one of your numbers'), which is far more specific than a bare name restatement. It doesn't explicitly contrast with sibling read_text_messages, which also surfaces SMS content, so an agent might briefly wonder which to use.

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?

'Call this right after a site says it sent you a code' gives an explicit trigger condition, which is exactly the timing an agent needs. It stops short of naming the alternative (read_text_messages) or stating when not to use it, so it lands at clear-context rather than full when/when-not guidance.

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.