Skip to main content
Glama
UserAd

didlogic_mcp

by UserAd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_allowed_ips

Retrieve a list of whitelisted IPs associated with a specific SIP account using JSON output. Use this tool to access and manage authorized IP configurations for secure communications.

Instructions

Get list of whitelisted IPs for a SIP account

Args: sipaccount_name: Name of SIP account

Returns a JSON object with array of whitelisted IP for SIP Account Example output: { "allowed_ips": [ "88.99.12.33" ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sipaccount_nameYes

Implementation Reference

  • src/didlogic_mcp/tools/allowed_ips.py:7-25 (handler)
    The handler function for the 'get_allowed_ips' MCP tool. It is decorated with @mcp.tool() for automatic registration and schema inference. Calls the Didlogic API to retrieve whitelisted IPs for the specified SIP account.
    @mcp.tool()
async def get_allowed_ips(
        ctx: Context,
        sipaccount_name: str | int = Field()
) -> str:
    """
        Get list of whitelisted IPs for a SIP account

        Args:
            sipaccount_name: Name of SIP account

        Returns a JSON object with array of whitelisted IP for SIP Account
        Example output: { "allowed_ips": [ "88.99.12.33" ] }
    """
    response = await base.call_didlogic_api(
        ctx, "GET",
        f"/v1/sipaccounts/{sipaccount_name}/allowed_ips"
    )
    return response.text
  • src/didlogic_mcp/server.py:101-101 (registration)
    Registers all tools from the allowed_ips module (including get_allowed_ips) with the FastMCP server instance.
    tools.allowed_ips.register_tools(mcp)

Tool Definition Quality

B3.1/5.0
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 states it 'Returns a JSON object' with an example, which adds some context on output format, but lacks details on permissions, rate limits, or error handling. This is inadequate for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is front-loaded with the core purpose, followed by structured sections for args and returns with an example. It's efficient and well-organized, though the example output could be slightly more detailed to enhance clarity without adding bulk.

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 no annotations, 0% schema coverage, and no output schema, the description provides basic purpose and parameter semantics but lacks comprehensive behavioral details. It's minimally viable for a simple retrieval tool but could improve with more context on usage or errors.

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 description adds meaningful context for the single parameter 'sipaccount_name' by explaining it as 'Name of SIP account', which clarifies its role beyond the schema's title. With 0% schema description coverage and only one parameter, this compensation is effective, though not exhaustive.

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 ('Get list') and resource ('whitelisted IPs for a SIP account'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_sip_account' or 'list_sip_accounts', which might also retrieve SIP account information, so it falls short of 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. For example, it doesn't mention if this is for retrieving only IP-related data as opposed to other SIP account details available in sibling tools, leaving the agent without context for selection.

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