Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Customer Users

list_customer_users
Read-onlyIdempotent

Retrieves all users associated with a specified customer ID, enabling assistants to inspect customer account membership and user details from IPEX.

Instructions

All users of a customer. IPEX API: GET /v1/customers/{customerId}/users.

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": {
      "customerId": "<customerId>"
    },
    "name": "list_customer_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesPath parameter 'customerId' 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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the concrete endpoint mapping (GET /v1/customers/{customerId}/users), which helps with API traceability, but says nothing about pagination, result ordering, or behavior for an unknown customerId.

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 followed by the endpoint reference, with no filler. It is terse but every sentence carries information.

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?

This is a simple single-parameter read tool with full annotation coverage and no output schema, so a short description is defensible. Still, it omits whether results are paginated or bounded and how an empty set is returned, leaving modest gaps for an agent.

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% with a single required customerId, so the schema already carries the parameter definition. The description only implies the id scopes the result set to one customer, adding no format or validation detail beyond that baseline.

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?

"All users of a customer" names the resource and the scoping relation (users belonging to a specific customer), which is enough to tell it apart from list_customers or list_services. The listing verb is only implied by the tool name rather than stated directly, so it stops short of a 5.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. that a valid customerId is required), and no pointer to sibling tools for other customer-related queries. An agent must infer usage entirely from the name and the schema.

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