Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Voip Credit

get_voip_credit
Read-onlyIdempotent

Retrieve the credit history for a landline VoIP number through the IPEX API to check account credit status and usage records.

Instructions

Credit history of a landline. IPEX API: GET /v1/voip/{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_voip_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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds the upstream IPEX endpoint for documentation mapping, but says nothing about what 'credit history' contains (limits, balances, entries), whether a missing number errors, or pagination.

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 short sentences with the resource scope front-loaded and no filler. The endpoint reference is arguably redundant with the tool name but earns its place for traceability to the upstream API.

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 single-parameter read tool with full annotation coverage and no output schema, the definition is minimally sufficient. It still leaves the agent guessing about the shape and meaning of the returned credit data, which the absent output schema would otherwise have carried.

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?

Only one parameter exists and schema description coverage is 100%, so the baseline is 3. The description adds the endpoint template showing 'number' as a path segment, but contributes no format detail (e.g., E.164 or national format) beyond the schema.

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 names a specific verb ('Credit history of...') and a specific resource ('a landline'), plus the exact upstream endpoint GET /v1/voip/{number}/credit. An agent can tell it retrieves credit data for a VoIP/landline number, distinct from the mobile-credit sibling, though the definition itself never names that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'of a landline' scopes it to VoIP numbers, so an agent can infer it is not for mobile credit. There is no explicit when-to-use, no prerequisite note (e.g., number must be a provisioned VoIP number), and no stated alternative such as get_mobile_credit.

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