Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Customers

list_customers
Read-onlyIdempotent

Retrieve IPEX B2B customer records and filter them by ID, TIN, city, name, login, hidden status, and billing dates, with pagination.

Instructions

Customer listing. IPEX API: GET /v1/customers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoQuery parameter 'id' of the IPEX API.
tinNoQuery parameter 'tin' of the IPEX API.
cityNoQuery parameter 'city' of the IPEX API.
noteNoQuery parameter 'note' of the IPEX API.
pageNoQuery parameter 'page' of the IPEX API.
typeNoQuery parameter 'type' of the IPEX API.
loginNoQuery parameter 'login' of the IPEX API.
hiddenNoQuery parameter 'hidden' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
streetNoQuery parameter 'street' of the IPEX API.
zipCodeNoQuery parameter 'zipCode' of the IPEX API.
externIdNoQuery parameter 'externId' of the IPEX API.
fulltextNoQuery parameter 'fulltext' of the IPEX API.
pageSizeNoQuery parameter 'pageSize' of the IPEX API.
customerNameNoQuery parameter 'customerName' of the IPEX API.
ipex_zpusobFakturaceNoQuery parameter 'ipex_zpusobFakturace' of the IPEX API.
ipex_datumFakturaceDoNoQuery parameter 'ipex_datumFakturaceDo' of the IPEX API.
ipex_datumFakturaceOdNoQuery parameter 'ipex_datumFakturaceOd' of the IPEX API.
ipex_zvysenaPozornostNoQuery parameter 'ipex_zvysenaPozornost' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 safety is fully covered elsewhere. The description adds nothing beyond the endpoint path — no mention of pagination behavior (page/pageSize), default result ordering, result caps, or what happens when no filters are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with zero waste in the literal sense, but the brevity is under-specification rather than efficiency: one sentence merely restates the title and the other restates the transport endpoint. Nothing about filtering or pagination is front-loaded because nothing is said at all.

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?

For a 19-parameter listing tool with no output schema, the description omits the information an agent most needs: how filters compose, pagination semantics, and result shape. The endpoint reference alone is insufficient context to invoke this tool confidently.

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 of 3 applies even though the description mentions no parameters. Note that the schema's own descriptions are tautological (e.g. "Query parameter 'ipex_zpusobFakturace' of the IPEX API"), leaving the meaning of the 19 filters, especially the Czech-named ipex_* fields, unexplained anywhere.

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 description states the resource (customers) and that it is a listing operation, plus the underlying endpoint GET /v1/customers. It does not differentiate this from siblings such as list_customer_users or list_services, which are also per-customer listings, so the purpose is only minimally clear.

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 when-to-use guidance at all: no mention of what the 19 query filters are for, whether filters combine as AND, or when to prefer this over other customer-related siblings. The endpoint reference is descriptive, not prescriptive.

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