Skip to main content
Glama
UserAd

didlogic_mcp

add_destination

Add a DID destination to a specified number on the didlogic_mcp server, configuring callhunt, active status, transport type (SIP, PSTN, or SIP account), and destination.

Instructions

Add a DID destination.

Args: number: DID number in DIDLogic 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) destination: destination

Returns a JSON object with did destination 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:

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoIs this destination active
callhuntNoIs it ring all group number
destinationYesDestination for DID
numberYesDID Number
transportNoTransport for destination

Implementation Reference

  • The handler function decorated with @mcp.tool(), defining and registering the 'add_destination' tool. It adds a destination to a DID number by posting to the DIDLogic API, including input schema via Pydantic Fields and comprehensive docstring for usage.
    @mcp.tool()
    async def add_destination(
        ctx: Context,
        number: str | int = Field(description="DID Number"),
        callhunt: bool = Field(
            description="Is it ring all group number", default=False
        ),
        active: bool = Field(
            description="Is this destination active", default=False
        ),
        transport: int = Field(
            description="Transport for destination", default=1
        ),
        destination: str | int = Field(description="Destination for DID")
    ) -> str:
        """
            Add a DID destination.
    
            Args:
                number: DID number in DIDLogic
                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)
                destination: destination
    
            Returns a JSON object with did destination 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:
            ```
            {
                "did_destination": {
                    "id": 1234455,
                    "destination": "12345",
                    "priority": 1,
                    "callhunt": false,
                    "active": true,
                    "transport": 5
                }
            }
            ```
        """
        data = {
            "destination[callhunt]": int(callhunt),
            "destination[active]": int(active),
            "destination[transport]": transport,
            "destination[destination]": destination
        }
        response = await base.call_didlogic_api(
            ctx, "POST", f"/v1/purchases/{number}/destinations",
            data=data
        )
        return response.text
Behavior3/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 clearly indicates this is a write operation ('Add'), describes the return format, and provides an example response. However, it doesn't mention important behavioral aspects like authentication requirements, error conditions, rate limits, or whether this operation is idempotent.

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 appropriately front-loaded with the core purpose, but includes redundant information. The 'transport' explanation appears twice (in both Args and Returns sections), and the example is quite lengthy. Some sentences could be more efficiently structured.

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?

For a write operation with no annotations and no output schema, the description does a good job covering the essentials: purpose, parameters with meaningful explanations, and a detailed return example. The main gaps are lack of error handling information and workflow context with sibling tools.

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 schema description coverage is 100%, so the baseline is 3. The description adds significant value by explaining the 'transport' parameter's numeric codes (1=SIP address, 4=PSTN, 5=SIP account) with examples, and clarifies the meaning of boolean flags ('callhunt' and 'active'). This goes well beyond what the schema provides.

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 action ('Add a DID destination') and resource ('DID destination'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'list_destinations' or 'delete_destination', which would be needed for a perfect score.

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. There's no mention of prerequisites, when this operation is appropriate, or how it relates to sibling tools like 'list_destinations' or 'delete_destination' in a workflow.

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