Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

List Invoice Item Ids

list_invoice_item_ids
Read-onlyIdempotent

Retrieves inserted invoice item IDs (hints) from the IPEX API, so you can identify available invoice items for follow-up queries or processing.

Instructions

List of inserted ids (hints). IPEX API: GET /v1/invoiceItem/idList.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. Beyond that, the description adds only the raw endpoint path; it does not clarify what 'inserted' means, whether the list is scoped to a tenant or time window, whether results are paginated, or what 'hints' implies about reliability of the ids.

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 fragments with no padding, and the core statement comes first. Brevity here tips into under-specification rather than efficiency, since '(hints)' consumes space without resolving meaning.

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

Completeness3/5

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

With no output schema and no parameters, the description is the only place to explain the return value, and it does so only partially ('list of inserted ids'). For a simple zero-argument read tool this is borderline adequate, but the ambiguity around 'inserted' and 'hints' leaves an agent unsure of what it will actually receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is trivially complete, so the baseline is 4. The description correctly implies no filtering inputs are available, consistent with the empty schema.

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 names a resource (invoice item ids) and an action (list), and pins the underlying endpoint GET /v1/invoiceItem/idList. However, the qualifier 'inserted ids (hints)' is cryptic — it is unclear whether these are recently created items, draft items, or partial identifiers — and nothing distinguishes it from siblings such as list_invoices or get_invoice_item.

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 statement of when to call this instead of list_invoices, get_invoice_item, or the other invoice-related siblings, and no preconditions. The agent must guess that this is a lightweight id-harvesting call.

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