Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Container Roaming Profiles

list_container_roaming_profiles
Read-onlyIdempotent

Lists roaming profiles for a specified container through the IPEX API, helping you inspect profile assignments before managing container settings.

Instructions

Roaming profiles of a container. IPEX API: GET /v1/containers/{containerId}/roamingProfiles.

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

Input Schema

NameRequiredDescriptionDefault
containerIdYesPath parameter 'containerId' 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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only the underlying API path, which is implementation detail rather than behavioral context such as pagination, result volume, or what a profile contains.

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 fragments with no filler and the resource stated first. It is efficient, though the second sentence is largely a documentation pointer rather than added meaning.

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 single-parameter read tool with rich annotations and no output schema, this is minimally adequate. However, nothing is said about the shape or size of the returned profile list, which an agent would need to plan a follow-up call.

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% with a single containerId path parameter already documented in the schema. The description adds no meaning beyond it, so the baseline of 3 applies.

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?

The phrase "Roaming profiles of a container" identifies the resource but omits an explicit verb, relying on the title and name for "list". It does differentiate from siblings like list_container_data_packs by naming a distinct resource, but the statement is close to a restatement of the tool name.

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 versus the many other list_container_* siblings, and no prerequisites or exclusions are stated. The agent must infer usage purely from the resource 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