Skip to main content
Glama

Dial by Aloha Labs

get_phone_number

Get a phone number for this agent. Returns your existing number if you already have one, otherwise provisions a new one. Use it when a website or service asks for a phone number.

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

Input Schema

NameRequiredDescriptionDefault
labelNoNote for yourself, e.g. 'signups'
api_keyYesYour Dial API key (from sign_up)
area_codeNoPreferred US/CA area code, e.g. 310
force_newNoProvision another number even if one exists

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 behavioral burden. It usefully discloses the idempotent get-or-create behavior, including that it may provision a new number as a side effect. However it says nothing about cost/credit consumption, permission or API-key requirements beyond the schema hint, rate limits, or whether provisioning is reversible.

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, front-loaded with the core behavior, followed by the return semantics and the usage trigger. Every sentence earns its place and there is no filler.

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?

For a 4-parameter tool with no output schema and no annotations, the description should say more about what comes back (number format, whether it's a full object) and the implications of provisioning (billing, limits). The 'returns your existing number' line hints at the return but leaves the agent guessing about side effects.

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 label, area_code, api_key and force_new are already documented in the schema. The description adds no parameter guidance (e.g. how area_code interacts with reusing an existing number, or when force_new is appropriate), so the 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 ('Get a phone number for this agent') and immediately clarifies the get-or-create semantics, which is the key differentiator from a plain provisioning call. It does not name the siblings it differs from (list_phone_numbers, release_phone_number), so it stops short of a 5.

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?

Gives an explicit trigger condition: 'Use it when a website or service asks for a phone number.' That is clear context for invoking it, but there are no exclusions or named alternatives (e.g. when to prefer list_phone_numbers to check for an existing number first).

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.