Skip to main content
Glama
UserAd

didlogic_mcp

by UserAd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_sip_account

Retrieve detailed SIP account information, including ID, caller ID, call limits, and IP restrictions, using a JSON response for streamlined account management.

Instructions

Get details about SIP account

Args: name: SIP account name

Returns a JSON object with SIP account details where: id: ID of SIP account name: SIP account name (login) callerid: CallerID associated with this SIP account label: label fot this SIP account charge: charge for calls on this month talk_time: total talk time for this month rewrite_enabled: do SIP account have calling number rewriting rule rewrite_cond: prefix to be rewrited (ex: 00) rewrite_prefix: prefix to what should be rewritten (ex: 44) didinfo_enabled: do DIDLogic will attempt send DID number as TO when receiving calls to this account ip_restrict: do we need to allowlist IP addresses for this account allowed_ips: IP addresses allowed for this SIP account call_restrict: flag indicates what SIP account should have maximum call time call_limit: maximum call duration in seconds channels_restrict: flag indicates what SIP account should have maximum channels limit max_channels: maximum sip channels cost_limit: flag indicates what SIP account should have maximum call cost max_call_cost: maximum call cost for this SIP account created_at: date of creation this SIP account

Example:

{
    "sipaccount": {
        "id": 61,
        "name": "12345",
        "callerid": "17254999999",
        "label": "TEST DEVICE",
        "host": "dynamic",
        "charge": "0.0",
        "talk_time": 0,
        "rewrite_enabled": false,
        "rewrite_cond": "8",
        "rewrite_prefix": "7",
        "didinfo_enabled": false,
        "ip_restrict": false,
        "call_restrict": true,
        "call_limit": 2800,
        "channels_restrict": false,
        "max_channels": 1,
        "cost_limit": false,
        "max_call_cost": "5.0",
        "created_at": "2024-06-03 06:06:47 UTC",
        "allowed_ips": ["1.2.3.4", "3.4.5.6"]
    }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of SIP account

Tool Definition Quality

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It effectively describes what data is returned (the JSON structure with all fields explained), which is good behavioral transparency for a read operation. However, it doesn't mention error conditions, authentication requirements, rate limits, or whether this is a read-only operation (though 'get' implies it).

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 becomes verbose with the exhaustive field-by-field explanation of the return object. While comprehensive, this detailed return value documentation might be better suited for an output schema. The example is helpful but lengthy.

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 simple read operation with 1 parameter and no output schema, the description provides excellent completeness by documenting all return fields with clear explanations. The example adds concrete value. However, without annotations covering safety/behavioral aspects, some gaps remain regarding error handling and operational constraints.

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 single parameter 'name' well-documented in the schema. The description adds minimal value beyond the schema by restating 'name: SIP account name' in the Args section. The baseline of 3 is appropriate since the schema already does the heavy lifting.

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 tool's purpose: 'Get details about SIP account' - a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'list_sip_accounts' or 'update_sip_account', 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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'list_sip_accounts' (for listing multiple accounts) or 'update_sip_account' (for modifying accounts), leaving the agent without context about appropriate usage scenarios.

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