Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Voip State

get_voip_state
Read-onlyIdempotent

Retrieve the current state of a VoIP or landline number via the IPEX API, optionally filtered by ICCID, to verify its status before service management.

Instructions

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

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_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
iccidNoQuery parameter 'iccid' 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

B3.3/5.0
Behavior3/5

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

The annotations already disclose that this is a read-only, idempotent, non-destructive, open-world operation. The description adds only that it is an IPEX API GET endpoint, without explaining what 'state' contains, error behavior, authentication needs, or response characteristics.

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

Conciseness5/5

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

The description is extremely concise and front-loads the core resource: 'Landline number state.' It contains no filler or redundant explanation beyond the endpoint reference.

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 simple two-parameter read tool with rich annotations and full schema coverage, the description is minimally adequate. However, with no output schema present, it does not explain what the returned 'state' represents or how the number and iccid parameters relate.

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 input schema already documents both number and iccid. The description only restates the path parameter in the endpoint URL and adds no further meaning about how iccid affects the query.

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 states a specific resource and action: retrieving the 'Landline number state' via GET /v1/voip/{number}/state. It is clear enough to distinguish landline state lookup from generic VoIP account tools, though it does not explicitly name or differentiate sibling tools.

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 gives no guidance on when to use this tool versus alternatives such as get_voip, get_phone_number_diagnostic, or get_mobile. The implied usage is only inferable from the tool name and endpoint, not from any stated context or exclusions.

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