Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Wholesale Invoices

list_wholesale_invoices
Read-onlyIdempotent

Retrieve wholesale invoices from IPEX with optional pagination, month filtering, and sorting to support billing review.

Instructions

List of wholesale invoices. IPEX API: GET /v1/wholesale-invoices.

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

Input Schema

NameRequiredDescriptionDefault
pageNoQuery parameter 'page' of the IPEX API.
monthsNoQuery parameter 'months' of the IPEX API.
orderByNoQuery parameter 'orderBy' of the IPEX API.
orderDirNoQuery parameter 'orderDir' of the IPEX API.
pageSizeNoQuery parameter 'pageSize' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. Beyond that the description adds only the endpoint path; it says nothing about pagination behavior, default result window, or how ordering defaults are applied despite exposing page/pageSize/orderBy/orderDir.

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?

Two short sentences, front-loaded with the resource, with no filler or redundancy. It is efficient but so terse that the terseness reflects under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a no-required-parameter read-only list with full annotation coverage and no output schema, so the description is close to sufficient. The remaining gaps, namely what an invoice record contains and how paging/ordering behave, are modest for a straightforward read operation.

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%, so the baseline is 3, but the schema entries are placeholder text ('Query parameter 'page' of the IPEX API') and the description adds no meaning about accepted formats, valid ordering fields, or what 'months' filters on. The description therefore neither helps nor harms beyond the structured fields.

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 says it lists wholesale invoices and maps to GET /v1/wholesale-invoices, which is a recognizable verb+resource. However, it largely restates the tool name and gives no basis for distinguishing it from siblings such as list_invoices or list_connector_invoices.

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, no prerequisites, and no mention of when a different invoice-listing tool would be the better choice. The only context is the underlying API endpoint, which does not help an agent choose between siblings.

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