Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Requests

list_requests
Read-onlyIdempotent

Retrieves IPEX order requests via GET /v1/requests, filtering by login, customer, status, type, or date range to review and track orders.

Instructions

Order list. IPEX API: GET /v1/requests.

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

Input Schema

NameRequiredDescriptionDefault
loginNoQuery parameter 'login' of the IPEX API.
detailNoQuery parameter 'detail' of the IPEX API.
changedToNoQuery parameter 'changedTo' of the IPEX API.
requestIdNoQuery parameter 'requestId' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
identifierNoQuery parameter 'identifier' of the IPEX API.
insertedToNoQuery parameter 'insertedTo' of the IPEX API.
changedFromNoQuery parameter 'changedFrom' of the IPEX API.
identifier2NoQuery parameter 'identifier2' of the IPEX API.
requestTypeNoQuery parameter 'requestType' of the IPEX API.
insertedFromNoQuery parameter 'insertedFrom' of the IPEX API.
requestStatusNoQuery parameter 'requestStatus' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the underlying endpoint and nothing about filtering behavior, pagination, default result volume, or auth requirements expected by an open-world API call.

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 with the endpoint, so there is no wasted wording, but the brevity comes from under-specification rather than economy. The fragment "Order list" is borderline unintelligible on its own.

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 12-parameter, zero-required, open-world list tool with no output schema, the description is far too thin — it explains neither the date-range filter pairs nor the shape of returned requests. Annotations salvage only the safety dimension.

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 baseline is 3, but the schema descriptions are pure tautologies ("Query parameter 'login' of the IPEX API") and the description compensates for none of it. Meaning for 12 filters such as changedFrom/changedTo, insertedFrom/insertedTo, detail, and requestStatus is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Order list" is a vague restatement that doesn't clearly say it retrieves request records or what a "request" is in this domain; the endpoint reference GET /v1/requests gives a hint of a read-list operation. Nothing distinguishes it from sibling list_* tools or the count-report siblings.

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 use this tool, when not to, or which sibling to prefer (e.g., the request count reports). An agent must infer usage from the name alone.

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