Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Mobile Credit

get_mobile_credit
Read-onlyIdempotent

Retrieve a mobile number's credit history from IPEX to verify credit status and support billing or risk decisions.

Instructions

Credit history of a mobile. IPEX API: GET /v1/mobile/{number}/credit.

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

Input Schema

NameRequiredDescriptionDefault
numberYesPath parameter 'number' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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 upstream endpoint mapping (IPEX GET /v1/mobile/{number}/credit), which corroborates the open-world hint but reveals nothing about what credit data is returned, freshness, or behavior for invalid numbers.

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 terse sentences, resource described first and the endpoint mapping second, with no filler. It is efficiently sized, though the endpoint reference borders on schema-restating detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with rich annotations and no output schema, the definition covers what the tool returns at a high level (credit history of a mobile). It leaves the composition of that history and the number format unstated, which are modest but real gaps.

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% and there is a single required 'number' path parameter, so the baseline is 3. The description adds no format guidance (E.164, national, with or without country prefix), which is the one parameter detail that would actually help.

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?

States a specific verb-resource pair: retrieval of a mobile number's credit history, and pins it to an IPEX endpoint. It implicitly distinguishes itself from get_voip_credit via 'of a mobile', but never explicitly contrasts the two, so it stops short of a 5.

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 call this versus the closely named sibling get_voip_credit, and no mention of prerequisites, when the credit data is meaningful, or failure conditions for unknown numbers. The agent must infer usage entirely 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