Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Phone Numbers

list_phone_numbers
Read-onlyIdempotent

Fetch a filtered list of IPEX phone numbers by number, customer, external ID, or search term, with pagination and ordering options, to review or manage VoIP and mobile inventory.

Instructions

List of phone numbers. IPEX API: GET /v2/phone-numbers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_phone_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoQuery parameter 'limit' of the IPEX API.
orderNoQuery parameter 'order' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
offsetNoQuery parameter 'offset' of the IPEX API.
searchNoQuery parameter 'search' of the IPEX API.
orderByNoQuery parameter 'orderBy' of the IPEX API.
showOpidNoQuery parameter 'showOpid' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
externalIdNoQuery parameter 'externalId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 data. The description adds only the raw endpoint reference and says nothing about pagination behavior, result size, or what the response contains — minimal added value beyond the annotations.

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?

Two short fragments, front-loaded with the resource and followed by the endpoint. There is no filler, though the extreme terseness borders on under-specification rather than genuine efficiency.

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?

A nine-parameter list tool with no output schema needs the description to cover pagination, filtering intent, and return shape, and it covers none of these. Given the density of sibling list tools, an agent lacks what it needs to invoke this one confidently.

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 all nine query parameters are documented in the schema itself, which sets the baseline at 3. The description contributes no additional meaning — it does not explain filtering semantics such as number, search, customerId, or how limit/offset/orderBy interact.

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 description identifies the resource (phone numbers) and that it is a listing operation, plus the underlying endpoint GET /v2/phone-numbers. It does not differentiate this tool from near-identical siblings such as list_phone_numbers_v1, list_connector_phone_numbers, or list_container_phone_numbers, so an agent cannot tell from the text which one to pick.

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 prerequisites, and no mention of when another listing tool would be preferable. The only contextual hint is the API path, which implies this is the v2 variant but never says so explicitly.

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