Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Tariff Plan

get_tariff_plan
Read-onlyIdempotent

Retrieve details for a specific IPEX tariff plan using its tariff plan ID and an optional type filter to support billing and service inquiries.

Instructions

Tariff plan detail. IPEX API: GET /v1/tariffPlans/{tariffPlanId}.

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

Input Schema

NameRequiredDescriptionDefault
typeNoQuery parameter 'type' 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 without the description. The description adds nothing beyond the raw HTTP verb and path — no note on error behavior when the ID is unknown, no indication of what the response contains, and no mention that this hits an external open-world API whose results may change.

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 zero filler, and the resource identification is front-loaded before the endpoint detail. It is efficient, though its brevity is partly under-specification rather than disciplined restraint.

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?

This is a simple two-parameter read tool, but there is no output schema, so the description should convey what a tariff plan record contains or at least its shape. It also gives no guidance on the optional 'type' filter, leaving the agent with little beyond the name and endpoint to work with.

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 both parameters are already documented as the IPEX path and query parameters. The description adds no meaning beyond the schema — the optional 'type' query parameter's valid values and effect are left entirely unexplained, which is a missed opportunity given there are no enums.

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?

"Tariff plan detail" is close to a restatement of the name, but the added endpoint "GET /v1/tariffPlans/{tariffPlanId}" makes clear this is a single-resource lookup by ID. That distinguishes it from list-oriented siblings such as list_tariff_plan_trunk_types and from get_tariff_plan_price, though the description never explicitly draws those distinctions.

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 when-to-use guidance, no mention of alternatives like get_tariff_plan_price, and no stated prerequisites such as needing a valid tariffPlanId. An agent must infer usage purely from the name and endpoint.

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