Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Pbx

list_pbx
Read-onlyIdempotent

Retrieve PBX information from IPEX and filter results by PBX ID, service ID, or customer ID to inspect configured phone systems.

Instructions

PBX info. IPEX API: GET /v1/pbx.

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

Input Schema

NameRequiredDescriptionDefault
idNoQuery parameter 'id' of the IPEX API.
serviceIdNoQuery parameter 'serviceId' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no pagination, authorization, scoping, or return-shape context for an open-world external API call.

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 wasted words, but the brevity is under-specification rather than efficiency — the endpoint reference leads while the actual purpose is never stated.

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 filtered list tool hitting an external IPEX API with optional query parameters, the description omits what is returned, whether results are filtered by the optional IDs, and any pagination or volume expectations. Annotations cover safety but not enough to compensate for the missing behavioral context.

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?

All three parameters are documented in the schema at 100% coverage, so the schema carries parameter semantics and the baseline of 3 applies. The description contributes nothing about how id, serviceId, or customerId filter results or whether they can be combined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"PBX info" restates the tool name rather than stating a specific verb and scope; the only added information is the upstream endpoint mapping "GET /v1/pbx", from which an agent must infer that this is a list/retrieve operation. Nothing distinguishes it from sibling list_* tools or explains what a PBX record contains.

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 list_services or list_containers, and no prerequisites or context are stated. Only the raw endpoint reference is provided, leaving usage entirely to inference from the name.

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