Skip to main content
Glama
UserAd

didlogic_mcp

by UserAd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

remove_purchased_did

Remove a purchased Direct Inward Dialing (DID) number from a DIDLogic account by specifying the number in E164 format. Returns detailed information about the removed DID, including ID, number, country, activation cost, and SIP codec.

Instructions

Remove DID from DIDLogic account

Args: number: DID number for removing in E164 format

Returns a JSON object with removed DID details where: dids: Array of removed dids where: id: ID of purchased DID number: number of DID country: Country name area: City name sms_enabled: Is number capable of receiving SMS channels: How many parallel channels have DID free_minutes: How many free minutes per month DID have activation: Activation cost for DID in USD monthly_fee: Monthly fee for DID per_minute: Per minute cost for DID origination_per_min: per minute cost if origin based rate applied requir_docs: required documents for activating number, where: 1 = Any form of ID 2 = Proof of address 3 = Proof of local address codec: what SIP codec is preferred for this number

Example:

{
    "dids": [
        {
            "id": 728070,
            "number": "17806999999",
            "sms_enabled": false,
            "no_local_cli": false,
            "channels": 4,
            "country": "Canada",
            "area": "Edmonton, AB",
            "free_minutes": 0,
            "codec": "G711",
            "require_docs": "",
            "activation": 1.0,
            "monthly_fee": 1.0,
            "per_minute": 0.01,
            "origination_per_min": 0.0
        }
    ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesNumber for remove from DIDLogic account

Implementation Reference

  • src/didlogic_mcp/tools/purchase.py:370-432 (handler)
    The core handler function decorated with @mcp.tool(), implementing the logic to remove a purchased DID by sending a DELETE request to the DIDLogic purchase endpoint.
    @mcp.tool()
async def remove_purchased_did(
    ctx: Context,
    number: str | int = Field(
        description="Number for remove from DIDLogic account"
    )
) -> str:
    """
        Remove DID from DIDLogic account

        Args:
            number: DID number for removing in E164 format

        Returns a JSON object with removed DID details where:
            dids: Array of removed dids where:
                id: ID of purchased DID
                number: number of DID
                country: Country name
                area: City name
                sms_enabled: Is number capable of receiving SMS
                channels: How many parallel channels have DID
                free_minutes: How many free minutes per month DID have
                activation: Activation cost for DID in USD
                monthly_fee: Monthly fee for DID
                per_minute: Per minute cost for DID
                origination_per_min: per minute cost if origin based rate applied
                requir_docs: required documents for activating number, where:
                    1 = Any form of ID
                    2 = Proof of address
                    3 = Proof of local address
                codec: what SIP codec is preferred for this number

        Example:
        ```
        {
            "dids": [
                {
                    "id": 728070,
                    "number": "17806999999",
                    "sms_enabled": false,
                    "no_local_cli": false,
                    "channels": 4,
                    "country": "Canada",
                    "area": "Edmonton, AB",
                    "free_minutes": 0,
                    "codec": "G711",
                    "require_docs": "",
                    "activation": 1.0,
                    "monthly_fee": 1.0,
                    "per_minute": 0.01,
                    "origination_per_min": 0.0
                }
            ]
        }
        ```
    """

    response = await base.call_didlogic_api(
        ctx, "DELETE",
        "/v2/buy/purchase",
        data={"did_numbers": number}
    )
    return response.text
  • src/didlogic_mcp/server.py:99-105 (registration)
    Server-wide registration of all tool modules, including 'tools.purchase.register_tools(mcp)' on line 103, which registers the 'remove_purchased_did' tool.
    tools.balance.register_tools(mcp)
tools.sip_accounts.register_tools(mcp)
tools.allowed_ips.register_tools(mcp)
tools.purchases.register_tools(mcp)
tools.purchase.register_tools(mcp)
tools.calls.register_tools(mcp)
tools.transactions.register_tools(mcp)

Tool Definition Quality

A3.5/5.0
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. It clearly indicates this is a destructive operation ('Remove'), but doesn't disclose critical behavioral traits like whether removal is permanent/reversible, authentication requirements, rate limits, error conditions, or side effects. The example response adds some value by showing the return format.

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 front-loaded with the core purpose, but includes extensive return value documentation that could be better handled by an output schema. The example is helpful but lengthy. Some sentences (like the detailed field explanations) could be more concise while maintaining 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?

For a destructive operation with no annotations and no output schema, the description does provide the return structure via example, which is valuable. However, it lacks important context about the operation's consequences, prerequisites, and error handling. The completeness is adequate but has clear gaps for a mutation tool.

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?

Schema description coverage is 100%, so the schema already documents the single parameter. The description adds minimal value beyond the schema by specifying the E164 format requirement and clarifying it's for 'removing' (consistent with schema's 'remove from'). With only one parameter, the baseline is appropriately high.

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 the specific action ('Remove DID from DIDLogic account') and identifies the resource (DID number). It distinguishes this tool from siblings like 'delete_sip_account' or 'delete_destination' by specifying it's for removing purchased DIDs specifically, not other account elements.

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. It doesn't mention prerequisites (e.g., DID must be purchased first), exclusions, or compare it to similar tools like 'delete_sip_account'. The agent must infer usage from the tool name alone.

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