Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Voip

get_voip
Read-onlyIdempotent

Retrieve landline VoIP number details through the IPEX API, with optional ICCID and detail parameters to refine the response.

Instructions

Landline number detail. IPEX API: GET /v1/voip/{number}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "get_voip"
  }
}

Input Schema

NameRequiredDescriptionDefault
iccidNoQuery parameter 'iccid' of the IPEX API.
detailNoQuery parameter 'detail' of the IPEX API.
numberYesPath parameter 'number' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured fields. The description adds only the upstream API route (GET /v1/voip/{number}), which is mild context but says nothing about what the response contains, what "detail" controls, or whether the call can fail for unknown numbers.

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?

Two short fragments with zero padding, and the resource is front-loaded. However, the brevity reflects under-specification rather than disciplined conciseness — the API-route sentence consumes space that could have carried behavioral or parameter meaning.

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?

The tool is a simple single-resource read with full schema coverage, no output schema, and annotations that already state the safety profile, so the description does not need to carry much. The main residual gap is that the semantics of the optional "detail" parameter remain unexplained anywhere.

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?

Schema description coverage is 100%, so the baseline is 3; the schema documents all three parameters. The description adds no meaning beyond what the schema already provides — notably it does not explain what the optional "detail" or "iccid" query parameters actually do, which is the one thing that would add value here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Landline number detail" identifies the resource (a landline/VoIP number) and implies a read of its details, but it is a noun phrase with no verb and no differentiation from siblings like get_voip_credit or get_voip_state. The endpoint reference confirms it is a single-resource fetch keyed by number, which is the most concrete signal present.

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?

There is no when-to-use guidance, no indication of what a "number" must be (E.164? national format? internal ID?), and no pointer to alternatives among the many get_voip_* and get_mobile/get_internet siblings. The agent must infer usage purely from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools