Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

list_numbers

List all phone numbers provisioned on your account to find forgotten numbers or audit active ones.

Instructions

List all phone numbers currently provisioned on this account. Useful when the agent needs to find a number it forgot about, or audit what's active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list_numbers' MCP tool handler function. Calls _client_or_init().list_numbers() and returns a dict of number dataclasses. Decorated with @mcp.tool() for registration.
    @mcp.tool()
    def list_numbers() -> dict:
        """List all phone numbers currently provisioned on this account. Useful when
        the agent needs to find a number it forgot about, or audit what's active.
        """
        try:
            numbers = _client_or_init().list_numbers()
            return {"numbers": [asdict(n) for n in numbers]}
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The tool is registered via the @mcp.tool() decorator on the list_numbers function (line 105). The FastMCP instance 'mcp' is created on line 47.
    @mcp.tool()
Behavior3/5

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

Since no annotations are provided, the description must disclose behavior. It correctly indicates a read operation but does not mention any limitations like pagination or rate limits, which is acceptable for a simple list tool.

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 sentences with no wasted words. The core purpose is front-loaded, and the usage guidance follows efficiently.

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 the tool's simplicity and lack of output schema, the description provides sufficient context for an agent to use it correctly, though it could optionally hint at the output structure.

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?

The input schema has no parameters, so the description does not need to add parameter details. The baseline score for 0 parameters is 4, and the description adequately implies that all numbers are returned.

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 clearly states 'List all phone numbers currently provisioned on this account,' which uses a specific verb and resource. It distinguishes well from sibling tools like provision_number or release_number.

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 provides explicit use cases: 'when the agent needs to find a number it forgot about, or audit what's active.' However, it does not mention when not to use the tool or alternatives.

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