Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Container Phone Numbers

list_container_phone_numbers
Read-onlyIdempotent

Retrieve phone numbers assigned to a specific IPEX container, with optional filters for number, status, trunk, customer, and payment type to inspect container telephony data.

Instructions

Phone numbers of a container. IPEX API: GET /v1/containers/{containerId}/phoneNumbers.

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": {
      "containerId": "<containerId>"
    },
    "name": "list_container_phone_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoQuery parameter 'detail' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
statusNoQuery parameter 'status' of the IPEX API.
trunkIdNoQuery parameter 'trunkId' of the IPEX API.
externIdNoQuery parameter 'externId' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
numberTypeNoQuery parameter 'numberType' of the IPEX API.
containerIdYesPath parameter 'containerId' of the IPEX API.
paymentTypeNoQuery parameter 'paymentType' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 safety is covered structurally. The description adds nothing beyond restating the HTTP verb and path – no pagination behavior, no note on how the many filters combine, no indication of result size for a container with many 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 no filler, and the resource is front-loaded. However, the brevity is under-specification rather than efficiency: the second sentence duplicates the tool name plus a URL instead of adding usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter read tool with no output schema, the description should explain at least the filter set and the container scoping. As written it says neither, so an agent must guess parameter meanings and cannot predict the response shape.

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 nominally 100%, so baseline is 3, but the schema text is purely boilerplate ("Query parameter 'detail' of the IPEX API") and gives no meaning for detail, numberType, paymentType or externId. The description does not compensate at all, leaving eight optional filter parameters semantically opaque.

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?

The phrase "Phone numbers of a container" plus the endpoint GET /v1/containers/{containerId}/phoneNumbers conveys that this lists phone numbers scoped to one container. It lacks a verb and does not distinguish itself from close siblings such as list_phone_numbers or list_connector_phone_numbers, leaving the agent to infer the container-scoping as the differentiator.

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 statement of when to use this tool, when to prefer list_phone_numbers or list_connector_phone_numbers, or what preconditions (a valid containerId) are needed. The endpoint path implies container scope but no explicit routing guidance is given.

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