Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Phone Number Diagnostic

get_phone_number_diagnostic
Read-onlyIdempotent

Retrieve diagnostic details for a phone number via the IPEX API to verify status and troubleshoot number-related issues.

Instructions

Number diagnostic detail. IPEX API: GET /v2/phone-numbers/diagnostic.

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": {
      "number": "<number>"
    },
    "name": "get_phone_number_diagnostic"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoQuery parameter 'full' of the IPEX API.
numberYesQuery parameter 'number' of the IPEX API (required).

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?

The annotations already declare this as a read-only, idempotent, open-world operation, so the safety profile is covered. Beyond that, the description only restates the HTTP endpoint and adds no context about authentication, rate limits, data freshness, or what the diagnostic result contains.

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?

The description is two short sentences with no filler and the resource is front-loaded. The endpoint reference is compact, though it is more useful to an API-aware developer than to an agent selecting among sibling tools.

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 two-parameter tool with rich annotations and no output schema, the description is still too sparse to guide correct selection and invocation. It does not explain what "diagnostic" covers, when this tool is preferable to sibling phone-number tools, or what the optional parameter does.

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 even though the description says nothing about the parameters. The description does not clarify the required phone number format or what the optional "full" parameter changes.

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 says "Number diagnostic detail" and names the IPEX endpoint, which identifies the resource area but not a clear action or diagnostic scope. It does not distinguish this tool from sibling phone-number tools such as list_phone_numbers or get_mobile, so an agent must infer what specific diagnostic information is returned.

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 guidance on when to use this diagnostic tool versus the many list/get siblings. The description provides no prerequisites, no exclusions, and no alternative-routing advice.

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