Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Invoices

list_invoices
Read-onlyIdempotent

Retrieve a customer's invoices to review billing data, with optional month-offset filtering via the IPEX API.

Instructions

Invoicing base data (list of services). IPEX API: GET /v1/invoices.

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

Input Schema

NameRequiredDescriptionDefault
customerIdYesQuery parameter 'customerId' of the IPEX API (required).
monthOffsetNoQuery parameter 'monthOffset' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/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 nothing beyond repeating the upstream endpoint — no pagination, result size, rate-limit, or what the invoice records actually contain, and the ambiguous "list of services" phrasing actually muddies behavior.

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 very short with no wasted words, and the endpoint reference is a useful anchor. But the first clause is cryptic and self-contradictory, so brevity comes at the cost of comprehension rather than from tight 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 an undocumented-in-prose monthOffset parameter, no output schema, and many similarly named invoice siblings, the description does far too little. An agent would know the endpoint but not what it returns or how to distinguish it from the connector invoice variants.

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 both parameters are documented and the baseline of 3 applies. The description adds no meaning on top — notably it never explains what monthOffset does (offset in months from now? which direction? default behavior?), leaving semantics entirely to a schema that only restates the raw API parameter name.

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?

The description says "Invoicing base data (list of services)" and cites GET /v1/invoices, which contradicts itself: the tool is named list_invoices but the parenthetical says it returns a list of services. An agent cannot tell from this whether the tool lists invoices or services, and nothing distinguishes it from siblings like list_connector_invoices or get_invoices_by_payment_type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 prerequisites, no mention of when to prefer this over list_connector_invoices / list_connector_invoices_all, and no statement of scope (all invoices vs. a customer's invoices). The only hint is the required customerId, which the agent must infer from 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