Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Containers

list_containers
Read-onlyIdempotent

Lists IPEX containers by type so you can retrieve available PBX containers for a specified category.

Instructions

List of containers (ústředny) by type. IPEX API: GET /v1/containers/{type}.

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": {
      "type": "<type>"
    },
    "name": "list_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesPath parameter 'type' 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the concrete API route, which is mildly useful, but says nothing about pagination, result volume, or whether an unknown 'type' errors or returns an empty list.

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 purpose and then the endpoint reference; nothing is padded. Very terse, but the brevity is not what limits the definition.

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-parameter read tool with rich annotations and no output schema, the definition is minimally viable. The notable gaps are the permissible values for 'type' and any indication of what the response contains or how it is paged.

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 coverage is 100%, so the baseline is 3, but the schema text for 'type' is merely 'Path parameter type of the IPEX API', which is circular. The description adds the meaning 'by type (of container)' but gives no hint of valid type values despite there being no enum, leaving the agent unable to populate the sole required parameter without external knowledge.

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 gives a clear verb-resource pair ('List of containers') plus a scoping qualifier ('by type') and even maps it to the underlying endpoint GET /v1/containers/{type}. It is distinguishable from sub-resource siblings such as list_container_simcards, though it never explicitly says so.

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 choose this tool versus the many sibling list tools (list_containers vs list_container_data_packs, list_container_flat_packs, etc.), nor any prerequisites or exclusions. The agent must infer usage purely 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