Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

release_number

Release a provisioned phone number to avoid ongoing Telnyx monthly charges. Use after finishing with the number to stop recurring fees.

Instructions

Release a previously provisioned phone number. Call this when done to avoid ongoing Telnyx monthly charges. Pass the E.164 phone_number returned by provision_number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYes

Implementation Reference

  • The `release_number` MCP tool handler. Decorated with @mcp.tool(), it takes a phone_number string, calls the Agentline SDK's release_number method, and returns a dict with phone_number and released status. Handles AgentlineError exceptions.
    @mcp.tool()
    def release_number(phone_number: str) -> dict:
        """Release a previously provisioned phone number. Call this when done to
        avoid ongoing Telnyx monthly charges. Pass the E.164 `phone_number` returned
        by `provision_number`.
        """
        try:
            released = _client_or_init().release_number(phone_number)
            return {"phone_number": phone_number, "released": released}
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • Registration via @mcp.tool() decorator on line 92, which registers `release_number` as an MCP tool with the FastMCP server instance.
    @mcp.tool()
  • Input schema: takes a single required string parameter `phone_number`. No type annotations beyond str. The return type is dict (untyped, dynamic).
    def release_number(phone_number: str) -> dict:
  • Helper usage inside `capture_code` (line 194): calls `client.release_number(number.phone_number)` to release a number after 2FA code capture.
    client.release_number(number.phone_number)
Behavior4/5

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

Discloses cost implication (avoid monthly charges). No annotations, but description adds key behavioral context. Lacks mention of irreversibility, but implied.

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 efficient sentences: first defines action, second gives when and how. No fluff.

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 simple tool with one parameter and no output schema, the description fully covers purpose, usage, and parameter source.

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

Parameters5/5

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

Adds meaning beyond schema: specifies E.164 format and that the value should come from 'provision_number'. Schema only says 'string'.

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?

Clearly states the action 'Release a previously provisioned phone number' with specific verb and resource. Distinguishes from sibling tools like 'provision_number'.

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

Usage Guidelines5/5

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

Explicitly tells when to use ('when done to avoid ongoing Telnyx monthly charges') and provides prerequisite ('Pass the E.164 phone_number returned by provision_number').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgottlieb84/agentline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server