Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Connector Phone Numbers

list_connector_phone_numbers
Read-onlyIdempotent

Retrieve phone numbers linked to a specific connector, with optional filters for number, status, category, and customer, to inspect connector telephony data.

Instructions

Phone numbers of a connector. IPEX API: GET /v1/connectors/{connectorId}/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": {
      "connectorId": "<connectorId>"
    },
    "name": "list_connector_phone_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoQuery parameter 'number' of the IPEX API.
statusNoQuery parameter 'status' of the IPEX API.
categoryNoQuery parameter 'category' 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.
connectorIdYesPath parameter 'connectorId' of the IPEX API.
containerIdNoQuery 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

B3.3/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, non-destructive, and open-world. The description adds the specific API endpoint and the fact that results are scoped to a connector, but it does not disclose pagination, ordering, authentication requirements, or how filters affect results.

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 two short sentences with no wasted wording. The resource scope is front-loaded, followed by the concrete API endpoint.

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 read-only list tool with nine parameters and no output schema, the description is minimally adequate: annotations cover safety, and the schema covers parameter presence. It still omits filter semantics and pagination behavior, which would help an agent invoke it correctly in a larger catalog.

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. However, the schema descriptions are mostly generic ("Query parameter 'number' of the IPEX API"), and the tool description adds no meaning about what the filters number, status, category, externId, customerId, numberType, containerId, or paymentType actually do.

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 identifies the resource and scope clearly: "Phone numbers of a connector," and the endpoint confirms it is a GET/list operation for that connector. It is not explicitly framed with a verb like "list" and does not differentiate itself from siblings such as list_phone_numbers or list_container_phone_numbers, but the purpose is still clear.

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 explicit when-to-use guidance, no alternatives, and no exclusions. It implies the tool is used with a connector because connectorId is required, but that is only inferable from the schema, not stated as usage guidance.

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