Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Container Simcards

list_container_simcards
Read-onlyIdempotent

Retrieve SIM cards linked to a given container, with optional filters for ICCID, status, full-text search, and result limit.

Instructions

SIM cards of a container. IPEX API: GET /v1/containers/{containerId}/simcards.

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

Input Schema

NameRequiredDescriptionDefault
iccidNoQuery parameter 'iccid' of the IPEX API.
limitNoQuery parameter 'limit' of the IPEX API.
statusNoQuery parameter 'status' of the IPEX API.
fulltextNoQuery parameter 'fulltext' of the IPEX API.
containerIdYesPath parameter 'containerId' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds only the HTTP verb and route, saying nothing about pagination, default ordering, how the query filters combine, or the shape of the returned list — minimal value beyond structured data.

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 clauses, front-loaded with the resource and followed by the API mapping — no filler. The brevity is efficient, though it borders on under-specification rather than tight writing.

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?

With no output schema, five parameters, untyped status/fulltext filters (no enums), and a listing that likely paginates, the description should explain filter behavior and result shape. It does none of that, leaving real gaps for an agent that needs to build a correct query.

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 schema already documents all five parameters, and the descriptions there merely restate 'Query parameter X of the IPEX API'. The tool description adds no filter semantics (e.g., what fulltext matches against, accepted status values, whether limit is a count or page size), which is consistent with the baseline 3 for full schema coverage.

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 names a specific resource in scope ('SIM cards of a container') and anchors it to the concrete IPEX endpoint GET /v1/containers/{containerId}/simcards. That implicitly separates it from siblings like list_container_data_packs and list_container_phone_numbers, though the listing verb is only implied by the noun phrase rather than stated.

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 other container sub-resource listings, no mention of that filters exist, and no prerequisites or exclusions. An agent must infer usage entirely from the tool name and the 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