Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Phone Numbers V1

list_phone_numbers_v1
Read-onlyIdempotent

Retrieve phone numbers from the deprecated IPEX API endpoint using filters for number, customer, external ID, search, and pagination.

Instructions

Deprecated list of phone numbers. IPEX API: GET /v1/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_v1"
  }
}

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

B3.3/5.0
Behavior3/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. The only behavioral addition is the deprecation status and the underlying REST endpoint, which is useful but thin; nothing is said about pagination, result ordering, or whether deprecated responses differ.

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 sentences with front-loaded deprecation status and zero filler. Appropriately sized, though the terseness contributes to the gaps in guidance rather than being purely economical.

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?

Nine optional query parameters, no output schema, and no explanation of response shape, pagination via limit/offset, or what deprecation means for callers. For a deprecated list endpoint with entirely self-referential parameter docs, the description does far too little to help an agent call it correctly.

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 coverage is 100%, but the schema descriptions are pure tautologies ("Query parameter 'limit' of the IPEX API") and the tool description adds no filter semantics, formats, or valid values. With nine optional query parameters and no enum hints, the baseline 3 applies because the schema at least enumerates them.

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?

"Deprecated list of phone numbers" gives a specific verb and resource, and the endpoint reference (GET /v1/phone-numbers) confirms a read-list operation. It does not distinguish itself from the sibling list_phone_numbers, which appears to be the non-deprecated equivalent, so an agent cannot tell from this text which one to prefer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "Deprecated" label implies a caution against use, which is weak when-to-use guidance, but the description never names the successor tool or states the conditions under which this endpoint should still be called. The agent must infer the alternative from sibling names alone.

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