Skip to main content
Glama

Hail Communication for AI

Release a number

release_number
DestructiveIdempotent

Permanently release a phone number after explicit user authorization.

    A mismatched ``confirm_e164`` returns an error without releasing anything.
    Calls and texts to a released number stop. Recovery is not guaranteed.
    Current and previous monthly fees remain due, without a refund.
    Pending orders cannot be released and return 409.
    A failed order was not purchased; this operation only dismisses it from the list.
    Returns ``released`` or ``dismissed``, plus ``number_id`` and ``e164``, or an error.
    

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": {
      "number_id": "<number_id>",
      "confirm_e164": "<confirm_e164>"
    },
    "name": "release_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
number_idYesWorkspace phone number ID, from ``list_numbers`` or ``acquire_number``.
confirm_e164YesThe number's ``e164`` value, such as ``+14155551234``, as a safety check.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive, idempotent and open-world, yet the description goes well beyond them: permanence, that calls/texts stop, that recovery is not guaranteed, that fees remain due without refund, a 409 on pending orders, and the dismiss-instead-of-release semantics for failed orders. It even specifies the return discriminators ('released' or 'dismissed' with number_id and e164). This is exactly the kind of consequence disclosure a destructive operation needs.

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?

The definition is front-loaded with the irreversible nature of the action, then proceeds through precondition failure, consequences, edge cases, and return values in short declarative lines. Each sentence carries distinct operational information with no filler or repetition.

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

Completeness5/5

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

For a destructive, irreversible tool this covers the essentials: authorization requirement, consequence of success, failure modes (mismatched confirm_e164, 409), the failed-order edge case, and result values. With an output schema present and full schema coverage, nothing an agent needs before invoking it is missing.

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 number_id and confirm_e164 are already documented, including that confirm_e164 is a safety check. The description adds only that a mismatch yields an error without side effects, which is a modest behavioral clarification rather than new parameter meaning. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

The opening sentence names a specific verb and resource ('Permanently release a phone number') and scopes it with a precondition ('after explicit user authorization'). It further disambiguates the operation from a related notion by explaining that a failed order is merely 'dismissed' rather than released. It stops short of explicitly naming any sibling (e.g., list_numbers, acquire_number, cancel_verification) as the alternative path, so it lands at 4 rather than 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?

The description gives a clear gating condition ('after explicit user authorization') and a case where the call does not apply ('Pending orders cannot be released and return 409'). It also clarifies the distinct case of failed orders, which are dismissed rather than released. There is no explicit statement of when to reach for a different tool instead, so it is clear context without true alternative routing.

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