Skip to main content
Glama

My invoices

portal_invoices_list
Read-onlyIdempotent

Your own invoices (commercial invoices and shop orders), newest first, with payment status, total per original currency and remaining amount. Filter by status, source, currency, date range (YYYY-MM-DD) or ref fragment. Page with next_cursor. Shop orders are detailed by get_my_order.

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": "portal_invoices_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
toNo
fromNo
limitNo
cursorNoValue of next_cursor from the previous page.
sourceNo
statusNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: default ordering ('newest first'), the meaning of 'total per original currency' versus 'remaining amount', and the pagination contract ('Page with next_cursor'). It does not state a max page size or what happens when filters match nothing, keeping it from a 5.

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

Conciseness5/5

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

Three compact clauses: what is listed and how it is shaped, what can be filtered, and how to page and get details. The ordering and scope constraints are front-loaded and every sentence adds information not present in structured fields.

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, the description usefully enumerates the returned fields and explains paging via next_cursor, and it points to get_my_order for shop-order detail. Given 8 parameters at 13% schema coverage, the only notable omission is the limit parameter's default/maximum and any note on empty results.

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?

Schema description coverage is only 13%, so the description must carry the burden, and it largely does: it maps q to a 'ref fragment', from/to to a date range with the YYYY-MM-DD format, and confirms status, source and currency as filters plus cursor for paging. The 'limit' parameter is never mentioned, which is the main residual gap at 8 parameters.

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 states the exact resource and scope: 'Your own invoices (commercial invoices and shop orders)', with ordering ('newest first') and the fields returned (payment status, total per original currency, remaining amount). It is clear what is listed, though it does not explicitly name sibling list/detail tools to contrast with, so it stops short of a 5.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a real routing hint — 'Shop orders are detailed by get_my_order' — and enumerates the supported filter axes, which implies when this tool fits. However, there is no explicit when-to-use/when-not statement against the other invoice tools or a note on when to page versus filter, so usage context is only partially covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources