Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Connector Invoices

list_connector_invoices
Read-onlyIdempotent

Retrieve billing invoices for a specific connector, with optional date range and detail filters.

Instructions

Billing list for one connector. IPEX API: GET /v1/connectors/{connectorId}/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": {
      "connectorId": "<connectorId>"
    },
    "name": "list_connector_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNoQuery parameter 'dateTo' of the IPEX API.
detailNoQuery parameter 'detail' of the IPEX API.
dateFromNoQuery parameter 'dateFrom' of the IPEX API.
connectorIdYesPath parameter 'connectorId' of the IPEX API.
monthOffsetNoQuery parameter 'monthOffset' of the IPEX API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 raw HTTP endpoint; it says nothing about pagination, result limits, date filtering behavior, or expected volume, which are the traits an agent would still need.

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 with the purpose front-loaded and no filler; the endpoint reference is compact and useful for technical callers. It is terse to the point of under-specification rather than verbose.

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?

With no output schema, a description ideally clarifies return shape and pagination behavior, and this one stays silent on those. However, the safety-relevant traits are already covered by annotations, so the practical gap for an agent to call this correctly is small.

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 five parameters are documented in the schema, and the description adds no semantics beyond naming connectorId as a path element. Baseline 3 applies when the schema does the heavy lifting, though dateFrom/dateTo/monthOffset usage remains unexplained anywhere.

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?

States a specific resource ('Billing list') scoped to 'one connector' and backs it with the exact endpoint GET /v1/connectors/{connectorId}/invoices, so an agent knows it returns invoices for a single connector. It does not explicitly contrast with siblings like list_connector_invoices_all or list_invoices, but the 'one connector' scoping implicitly separates it from the all-connectors variant.

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 over list_connector_invoices_all, list_invoices, or list_wholesale_invoices. The 'one connector' phrase hints at scope, but no conditions or alternatives are named, leaving the agent to infer selection from the tool 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