Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Ict Price List Item

get_ict_price_list_item
Read-onlyIdempotent

Retrieve a specific ICT price list item by its ID from IPEX to view pricing details for a product or service.

Instructions

Get pricelist item. IPEX API: GET /v1/ictPriceList/items/{itemId}.

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": {
      "itemId": "<itemId>"
    },
    "name": "get_ict_price_list_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesPath parameter 'itemId' 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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only the upstream endpoint mapping and nothing about error behavior when an itemId is unknown or about what data comes back.

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, front-loaded sentences with no filler; the action comes first and the endpoint mapping follows. The endpoint reference is borderline redundant but serves as useful provenance.

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 one-parameter read getter with full annotation coverage, the definition is minimally adequate. With no output schema present, it would benefit from a brief note on what the returned item contains, since nothing else supplies that.

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% for the single itemId path parameter, so the schema carries the meaning. The description merely echoes that it is a path parameter via the endpoint template and adds no format, sourcing, or lookup hints.

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 and resource ('Get pricelist item') and pins it to the exact API endpoint GET /v1/ictPriceList/items/{itemId}, which distinguishes item-level retrieval from the list-level sibling get_ict_price_list. It stops short of explicitly naming sibling alternatives.

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 preconditions, and no mention of when to prefer get_ict_price_list or list_ict_price_lists instead. The agent must infer selection purely from the singular 'item' noun.

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