Skip to main content
Glama

Dial by Aloha Labs

release_phone_number

Give up a phone number you no longer need. You will stop receiving texts on it.

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

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Dial API key (from sign_up)
number_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses one consequence (you stop receiving texts) but says nothing about irreversibility, whether the number is permanently deleted or reclaimed by the provider, whether it can be restored, or what happens to message history — critical gaps for a destructive mutation.

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 short sentences, action first and consequence second, with zero filler. Appropriately sized for what little it chooses to say.

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

Completeness2/5

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

A destructive release operation with no annotations, no output schema, and an undocumented required identifier. The description leaves an agent unable to determine reversibility or how to obtain number_id, which is inadequate for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: api_key is documented in the schema, but number_id has no description anywhere. The description could have said number_id comes from list_phone_numbers or get_phone_number, but adds no parameter meaning at all.

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: giving up (releasing) a phone number. It's clearly distinct in kind from siblings like get_phone_number or list_phone_numbers, though it never explicitly names that contrast or clarifies whether it deletes the number record versus merely unassigning it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"A phone number you no longer need" implies the triggering condition but gives no explicit guidance on prerequisites (e.g., that the number must belong to your account), no alternatives, and no caution about when not to call it.

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.