Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Services

list_services
Read-onlyIdempotent

Retrieve IPEX services with optional filters such as status, customer, number, and payment type to find and review service records.

Instructions

List of services. IPEX API: GET /v1/services.

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

Input Schema

NameRequiredDescriptionDefault
detailNoQuery parameter 'detail' of the IPEX API.
numberNoQuery parameter 'number' of the IPEX API.
resultNoQuery parameter 'result' of the IPEX API.
statusNoQuery parameter 'status' of the IPEX API.
externIdNoQuery parameter 'externId' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
numberTypeNoQuery parameter 'numberType' of the IPEX API.
containerIdNoQuery parameter 'containerId' of the IPEX API.
paymentTypeNoQuery parameter 'paymentType' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no return shape, no pagination behavior, no note on what the nine filters do or what an empty result means.

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

Conciseness3/5

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

It is short and front-loaded, so nothing is wasted, but the first sentence is essentially a restatement of the tool name and the second is a bare endpoint path. Brevity here reflects under-specification rather than disciplined editing.

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 tool with nine optional filter parameters, no output schema, and an open-world backend, the description omits everything an agent would need beyond the schema: what fields the filters match, whether results are paginated, and roughly what a service record contains. It is not adequate for this complexity.

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%, and each of the nine query parameters carries a schema description (albeit generic ones like "Query parameter 'detail' of the IPEX API"). With the schema doing all the work the baseline of 3 applies; the description contributes no additional parameter meaning such as accepted values or filtering semantics.

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?

"List of services" plus the endpoint mapping (GET /v1/services) tells the agent this is a read-only enumeration of services, which is more than the name alone. But it never distinguishes it from siblings like list_shared_services or search_services_fulltext, so the agent cannot tell which listing tool to pick.

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 statement about what kind of services are returned, when to prefer this over the shared-services or fulltext-search variants, or any prerequisite. The endpoint reference is documentation, not guidance.

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