Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Mobile

get_mobile
Read-onlyIdempotent

Retrieves IPEX mobile number details for a specified number, with optional ICCID and detail query parameters, by calling GET /v1/mobile/{number}.

Instructions

Mobile number detail. IPEX API: GET /v1/mobile/{number}.

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

Input Schema

NameRequiredDescriptionDefault
iccidNoQuery parameter 'iccid' of the IPEX API.
detailNoQuery parameter 'detail' of the IPEX API.
numberYesPath parameter 'number' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only the raw endpoint path and says nothing about what is returned, how an unknown number is handled, or what the iccid/detail flags change.

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?

It is short and front-loaded, but the second sentence mostly restates the path template already implied by the required 'number' parameter. Brevity here reflects under-specification rather than efficient communication.

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?

With no output schema, the description is the only place an agent could learn what the returned 'detail' payload looks like, and it never says. The two optional query parameters (iccid, detail) are also left semantically unexplained.

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 schema documents all three parameters, albeit with boilerplate text. The description adds no meaning beyond that, so the high-coverage baseline of 3 applies.

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?

"Mobile number detail" identifies the resource (a mobile number) and implies a read/lookup, but uses no specific verb and gives no hint of what 'detail' contains. It does nothing to distinguish it from siblings such as get_mobile_credit or get_phone_number_diagnostic.

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 contains no when-to-use or when-not-to-use guidance and names no alternative tool. An agent must infer that this is the general detail lookup versus the credit- or diagnostic-specific siblings.

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