Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Container Data Packs

list_container_data_packs
Read-onlyIdempotent

Retrieve the data packs assigned to an IPEX container by container ID, with optional filtering by data pack type or tariff plan.

Instructions

Data packs of a container. IPEX API: GET /v1/containers/{containerId}/dataPacks.

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

Input Schema

NameRequiredDescriptionDefault
typeNoQuery parameter 'type' of the IPEX API.
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.7/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. The description adds only the raw IPEX endpoint mapping; it says nothing about result shape, pagination, ordering, or what happens with an unknown containerId, so behavior beyond annotations is essentially undisclosed.

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 resource and then the API mapping, with no filler. It is terse rather than bloated, though the fragment style leaves the purpose slightly under-stated.

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 three-parameter read-only list tool with full schema coverage and annotations, the definition is minimally workable. It still omits whether results are paginated or how an invalid containerId behaves, which an agent would need before calling reliably.

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 (containerId, type, tariffPlanId) are already documented in the schema and the baseline of 3 applies. The description adds no meaning beyond that — it does not explain what values 'type' or 'tariffPlanId' accept or how filtering interacts.

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?

"Data packs of a container" identifies the resource and its parent scope, but it is a noun fragment with no verb, so listing is only implied. It does not distinguish this from close siblings such as list_container_flat_packs or list_container_simcards, leaving the agent to infer that this returns data-pack objects.

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 tool, what prerequisites exist (e.g., a valid containerId), or which sibling to choose for related container resources. The endpoint line implies a read of a container's data packs but nothing more.

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