Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Ict Price List

get_ict_price_list
Read-onlyIdempotent

Retrieve details for a specific ICT price list by ID to review pricing and verify offered rates.

Instructions

Get pricelist detail. IPEX API: GET /v1/ictPriceList/{id}.

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": {
      "id": "<id>"
    },
    "name": "get_ict_price_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter 'id' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 covered. The description adds only a raw REST path and says nothing about what happens when the id is unknown, what fields come back, or whether the upstream call is external/rate-limited despite openWorldHint=true.

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 operation and followed by the endpoint reference; nothing is padded. It is terse to the point of under-informing, but no sentence is wasted.

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 simple single-record read with full annotation coverage and a fully described one-parameter schema, this is minimally adequate. With no output schema present, the description arguably should say something about the returned shape, and it never addresses failure modes.

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% and the single required parameter 'id' is documented as a path parameter, so the schema does the heavy lifting. The description adds no meaning beyond that, which is the baseline case for a fully covered 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 and resource ("Get pricelist detail") and pins it to an exact endpoint, GET /v1/ictPriceList/{id}, so the agent knows this is a single-record fetch by id. It does not, however, distinguish this from the sibling get_ict_price_list_item, which a reader must infer from the name alone.

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 use this tool versus list_ict_price_lists or get_ict_price_list_item, and no prerequisite or context guidance. Usage must be inferred entirely from the name and endpoint path.

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