Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Tariff Plan Price

get_tariff_plan_price
Read-onlyIdempotent

Retrieve the price for a specific IPEX tariff plan by tariff plan ID, optionally filtering by number and CDR type.

Instructions

Price of a tariff plan. IPEX API: GET /v1/tariffPlans/{tariffPlanId}/price.

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": {
      "tariffPlanId": "<tariffPlanId>"
    },
    "name": "get_tariff_plan_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoQuery parameter 'number' of the IPEX API.
cdrTypeNoQuery parameter 'cdrType' of the IPEX API.
tariffPlanIdYesPath parameter 'tariffPlanId' of the IPEX API.

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the underlying REST endpoint, which does not tell the agent anything about pricing semantics (one-off vs recurring, currency, validity) or how the optional filters alter results.

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, front-loaded with the purpose and then the backing endpoint, with no filler. The brevity is efficient, though it borders on under-specification rather than being genuinely tight prose.

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 tool with three parameters, one required, no output schema, and an open-world read, the definition is too thin: it does not explain what "price" returns, how the optional filters affect the result, or what happens for an unknown tariffPlanId. The endpoint reference alone does not complete the picture an agent needs.

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 all three parameters are documented in the schema, which sets the baseline at 3. However, those schema descriptions are tautological ("Query parameter 'number' of the IPEX API"), and the tool description does nothing to clarify what number or cdrType actually filter, so no value is added beyond the structured fields.

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?

"Price of a tariff plan" is a noun phrase rather than a verb+resource, but combined with the endpoint path it does convey that this retrieves pricing for a specific tariff plan. It is distinguishable from get_tariff_plan in intent, yet the definition never states the verb or the scope (single plan vs list) explicitly, leaving the agent to infer retrieval.

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 instead of get_tariff_plan or the price-list siblings such as get_ict_price_list. No prerequisites, no exclusions, and no mention of what the optional number/cdrType filters are for.

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