Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Invoices Print

get_invoices_print
Read-onlyIdempotent

Generate printable invoice base data for a payment type and file format, with optional customer, include, and month-offset filters.

Instructions

Printable output of invoicing base data. IPEX API: GET /v1/invoices/{paymentType}/{fileFormat}.

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": {
      "paymentType": "<paymentType>",
      "fileFormat": "<fileFormat>"
    },
    "name": "get_invoices_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoQuery parameter 'include' of the IPEX API.
customerIdNoQuery parameter 'customerId' of the IPEX API.
fileFormatYesPath parameter 'fileFormat' of the IPEX API.
monthOffsetNoQuery parameter 'monthOffset' of the IPEX API.
paymentTypeYesPath parameter 'paymentType' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the underlying HTTP endpoint and the notion of printable output, which is useful context, but says nothing about response media type (PDF/binary?), size, or cost of the call.

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

Conciseness4/5

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

Two short sentences, output characterization front-loaded before the endpoint reference, with no filler. It is efficient, though the terseness leaves gaps that additional clauses could have filled.

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?

With five parameters, no enums, no output schema, and a print/export semantic, an agent needs to know which fileFormat and paymentType values are legal and what is returned. The description covers neither, so calling it correctly still requires guessing or trial and error.

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 nominally 100%, but the schema descriptions are tautologies ('Path parameter of the IPEX API'), so real semantics come only from parameter names. The description confirms paymentType and fileFormat are path parameters via the endpoint template but supplies no valid values for either, and monthOffset/include remain unexplained; baseline 3 applies given high coverage.

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

Purpose4/5

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

The description names a concrete verb+resource (printable output of invoice base data) and pins it to a specific endpoint, GET /v1/invoices/{paymentType}/{fileFormat}, which tells an agent this is the print/export variant of invoices. It stops short of differentiating it from siblings like get_invoices_by_payment_type or list_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 mention of when to pick this over the other invoice tools, and no prerequisites or exclusions. The agent must infer from the word 'printable' that this is for generating print-ready output.

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