Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Voip Profiles

list_voip_profiles
Read-onlyIdempotent

List landline VoIP profiles in an IPEX account to review available profile configurations before assigning numbers or managing VoIP settings.

Instructions

List of landline profiles. IPEX API: GET /v1/voip/profiles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 structurally. The description adds only the underlying REST endpoint (GET /v1/voip/profiles), which gives no behavioral context such as pagination, rate limits, or whether the list is account-scoped.

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 compact sentences with the resource stated first, so the essential fact is front-loaded. The endpoint sentence is of marginal value to an agent but is short and does not obscure the purpose.

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 simple zero-parameter list tool with full annotation coverage and no output schema, the description is minimally sufficient to call it correctly. However, it says nothing about what a profile contains or whether results are paginated, which is the only remaining gap an agent might hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related information is missing or misleading.

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 concretely as 'landline profiles' and the operation as listing, which is enough to distinguish it from the get_voip/get_voip_state siblings. It does not explicitly differentiate from list_container_roaming_profiles or similar list tools, and the shift from the tool name's 'voip' to 'landline' introduces a small naming mismatch an agent must reconcile.

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 call this versus get_voip or get_voip_state, no mention of prerequisites, and no exclusions. The agent must infer that this is the enumeration counterpart to the single-object get_voip tool.

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