Skip to main content
Glama
UserAd

didlogic_mcp

list_destinations

Retrieve and manage DID destinations via JSON output, including ID, destination, priority, callhunt status, activation, and transport type.

Instructions

List DID destination.

Args: number: DID number in DIDLogic

Returns a JSON object with all did destinations where: id: ID of destination destination: destination priority: priority of selection callhunt: flag indicates do destination is part of ring all group active: flag indicates is destination enabled or not transport: transport of destination where: 1 = SIP address destination (ex: 123@example.com) 4 = PSTN (phone number) destination (ex: 15551231233) 5 = SIP account destination (ex: 12345)

Example:

{
    "destination": [
        {
            "id": 1234455,
            "destination": "12345",
            "priority": 1,
            "callhunt": false,
            "active": true,
            "transport": 5
        }
    ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesDID Number

Implementation Reference

  • The core handler function for the 'list_destinations' tool. It takes a DID number and retrieves the list of destinations via the DIDLogic API using the base helper. The @mcp.tool() decorator handles registration.
    @mcp.tool()
    async def list_destinations(
            ctx: Context,
            number: str | int = Field(description="DID Number")
    ) -> str:
        """
            List DID destination.
    
            Args:
                number: DID number in DIDLogic
    
            Returns a JSON object with all did destinations where:
                id: ID of destination
                destination: destination
                priority: priority of selection
                callhunt: flag indicates do destination is part of ring all group
                active: flag indicates is destination enabled or not
                transport: transport of destination where:
                    1 = SIP address destination (ex: 123@example.com)
                    4 = PSTN (phone number) destination (ex: 15551231233)
                    5 = SIP account destination (ex: 12345)
    
            Example:
            ```
            {
                "destination": [
                    {
                        "id": 1234455,
                        "destination": "12345",
                        "priority": 1,
                        "callhunt": false,
                        "active": true,
                        "transport": 5
                    }
                ]
            }
            ```
        """
    
        response = await base.call_didlogic_api(
            ctx,
            "GET",
            f"/v1/purchases/{number}/destinations"
        )
        return response.text
  • Top-level registration call that invokes register_tools on the purchases module, thereby registering the list_destinations tool among others.
    tools.purchases.register_tools(mcp)
  • Uses the base.call_didlogic_api helper function to perform the API call for listing destinations.
    response = await base.call_didlogic_api(
        ctx,
        "GET",
        f"/v1/purchases/{number}/destinations"
    )
    return response.text
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format and example, which is helpful, but lacks critical behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, or error handling. The description does not contradict annotations, but it is insufficient for a mutation-sensitive context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with sections for Args, Returns, and an Example, which is organized. However, it includes verbose details in the return explanation and example that could be more succinct, and the front-loaded purpose statement is brief but not maximally efficient. Some sentences, like the detailed return field descriptions, could be condensed without losing clarity.

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

Completeness3/5

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

Given the tool has 1 parameter with full schema coverage and no output schema, the description provides a clear purpose, return format, and example, which is adequate for a simple list tool. However, it lacks behavioral context (e.g., safety, limits) and usage guidelines, making it incomplete for optimal agent decision-making in a server with multiple related tools.

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?

The schema description coverage is 100%, with the parameter 'number' documented as 'DID Number'. The description adds minimal value by restating 'DID number in DIDLogic', which is slightly redundant. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not significantly enhance parameter understanding beyond the schema.

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 description clearly states the verb ('List') and resource ('DID destination'), making the purpose specific and understandable. However, it does not explicitly differentiate this tool from sibling tools like 'get_sip_account' or 'list_sip_accounts', which might also retrieve related information, leaving some ambiguity in sibling differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as 'list_sip_accounts' or 'get_sip_account', nor does it mention any prerequisites or exclusions. It only describes what the tool does, without contextual usage 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

Related 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/UserAd/didlogic_mcp'

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