Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

provision_number

Provision a phone number for receiving SMS, sending messages, or making voice calls. Specify a phone number or area code to get an E.164 number for 2FA or outbound calls. Save the returned number for later use.

Instructions

Provision a phone number the agent can use — for receiving SMS (e.g. 2FA), sending SMS, or placing/receiving voice calls.

Use this BEFORE signing up for a service that asks for a phone number, or before making outbound calls. If phone_number is given, provisions that specific number; otherwise auto-searches by area_code.

Returns a dict with id, phone_number (E.164 format — pass this to forms), provider, and status. Save the returned phone_number — you need it to later release_number or wait_for_sms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
area_codeNo
country_codeNoUS
phone_numberNo

Implementation Reference

  • The main handler function for the 'provision_number' MCP tool. It is decorated with @mcp.tool() to register it as an MCP tool, accepts optional area_code, country_code (default "US"), and phone_number parameters, delegates to the Agentline SDK client, and returns the result as a dict.
    @mcp.tool()
    def provision_number(
        area_code: str | None = None,
        country_code: str = "US",
        phone_number: str | None = None,
    ) -> dict:
        """Provision a phone number the agent can use — for receiving SMS (e.g. 2FA),
        sending SMS, or placing/receiving voice calls.
    
        Use this BEFORE signing up for a service that asks for a phone number, or
        before making outbound calls. If `phone_number` is given, provisions that
        specific number; otherwise auto-searches by `area_code`.
    
        Returns a dict with `id`, `phone_number` (E.164 format — pass this to forms),
        `provider`, and `status`. Save the returned `phone_number` — you need it to
        later `release_number` or `wait_for_sms`.
        """
        try:
            result = _client_or_init().provision_number(
                phone_number=phone_number,
                area_code=area_code,
                country_code=country_code,
            )
            return asdict(result)
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The tool is registered with FastMCP via the @mcp.tool() decorator on line 64. The mcp instance is created at line 47 (mcp = FastMCP('agentline')).
    @mcp.tool()
    def provision_number(
  • Input parameters: area_code (optional string), country_code (default 'US'), phone_number (optional string). Return type is dict.
    def provision_number(
        area_code: str | None = None,
        country_code: str = "US",
        phone_number: str | None = None,
    ) -> dict:
Behavior4/5

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

No annotations provided, so the description carries full burden. It clearly states that the tool provisions a number, returns a dict with specific fields (id, phone_number, provider, status), and mentions E.164 format. It also describes conditional behavior based on phone_number parameter. Minor omission: no mention of potential rate limits or authentication requirements, but the action is inherently non-destructive and well-explained.

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 description is two well-structured paragraphs. First paragraph clearly states purpose and use cases. Second paragraph explains parameters, return value, and provides a crucial note to save the phone_number. Every sentence adds value; no fluff.

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

Completeness4/5

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

Given 3 parameters, no output schema, and no annotations, the description is comprehensive. It explains return fields, E.164 format, and references sibling tools (release_number, wait_for_sms). Missing details about limitations (e.g., provider availability, cost) but still sufficient for typical use.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well. It explains the logic: if phone_number is given, provision that specific number; otherwise auto-search by area_code. It also describes the return value fields. However, it does not explicitly mention the country_code parameter (default 'US'), leaving a slight gap. Overall, adds significant meaning beyond the schema.

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?

The description uses a clear verb 'Provision' and specifies the resource 'a phone number'. It explains the tool's capabilities (receiving SMS, sending SMS, voice calls) and distinguishes it from sibling tools like list_numbers (listing) and release_number (releasing). The purpose is unambiguous.

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?

Provides explicit when-to-use guidance: 'Use this BEFORE signing up for a service that asks for a phone number, or before making outbound calls.' It also explains the two modes (specific number vs. auto-search) and tells the user to save the returned phone_number for later use with release_number or wait_for_sms. This is excellent contextual advice.

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