Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Mobile Portation Dates

list_mobile_portation_dates
Read-onlyIdempotent

Lists available mobile portation dates for a given CVOP, helping users select a valid porting day via IPEX.

Instructions

Possible porting days. IPEX API: GET /v1/mobile/availablePortationDates/{cvop}.

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": {
      "cvop": "<cvop>"
    },
    "name": "list_mobile_portation_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvopYesPath parameter 'cvop' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered elsewhere. The description adds nothing beyond the raw endpoint path: no explanation of what a porting day is, whether results are time-bounded, or how cvop affects scope.

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 fragments with no filler, and the substantive statement comes first. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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?

The tool is a simple read with one fully documented parameter and complete annotations, so much of the burden is elsewhere. However, there is no output schema and the description never hints at return shape (a list of dates, in what format or window), leaving the agent to guess what comes back.

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 coverage is 100% with a single documented cvop path parameter, so the baseline of 3 applies. The description only echoes that cvop is a path segment in the URI; it does not clarify whether cvop is a mobile identifier, an operator code, or something else.

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?

"Possible porting days" is a near-tautological restatement of the name, softened only by the API mapping that reveals it reads available portation dates for a given cvop. It never distinguishes the tool from siblings such as get_mobile, and a fragment alone would be too vague to act on without the endpoint path.

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_mobile or any other listing tool, and no mention of prerequisites such as needing an existing mobile or cvop. The agent must infer the use case entirely from the tool 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