Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Container Flat Packs

list_container_flat_packs
Read-onlyIdempotent

Lists flat packs for a specified container via the IPEX API, with an optional tariff plan filter, to support container flat-pack lookups.

Instructions

Flat packs of a container. IPEX API: GET /v1/containers/{containerId}/flatPacks.

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": {
      "containerId": "<containerId>"
    },
    "name": "list_container_flat_packs"
  }
}

Input Schema

NameRequiredDescriptionDefault
containerIdYesPath parameter 'containerId' of the IPEX API.
tariffPlanIdNoQuery parameter 'tariffPlanId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description only adds the GET endpoint path, offering nothing about pagination, result limits, or what is returned — the read path of the IPEX API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with no filler, so it is concise, but the brevity comes at the cost of substance — there is no front-loaded statement of purpose or behavior.

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 read-only listing tool with two params and no output schema, the description should at least indicate what a flat pack is and whether results are paginated. Neither is present, leaving the definition thin despite the helpful annotations.

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 containerId and tariffPlanId are documented in the schema itself. The description adds no meaning beyond that, which matches the baseline 3 for fully-covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Flat packs of a container" merely restates the tool name/title without a verb or scope qualifier; the only added information is the underlying HTTP endpoint. It does not explain what a flat pack is or how this listing differs from the many sibling list tools.

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?

No when-to-use guidance is given, and no alternatives are mentioned despite many closely related siblings (list_container_data_packs, list_container_simcards, list_container_roaming_profiles). The agent must infer that this tool is the container-scoped listing of flat packs purely from the name.

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