Skip to main content
Glama

MaxRechnung

Zahlungseingänge auflisten

list_payments
Read-only

Tarif: ab Business (darunter antwortet die API mit plan_required).

Zahlungseingänge auflisten

Erfasste Zahlungseingänge, neueste zuerst. Mit invoice_id auf eine Rechnung einschränken.

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

Input Schema

NameRequiredDescriptionDefault
limitNoQuery-Parameter limit
offsetNoQuery-Parameter offset
invoice_idNoNur Zahlungseingänge dieser Rechnung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds value beyond that: the plan-tier gate and its error behavior (plan_required) plus the default sort order (newest first). It does not cover result shape or how limit/offset interact, but the added context is meaningful.

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?

Three short lines, front-loaded with the plan constraint and then the operation and its scoping. The repeated heading line 'Zahlungseingänge auflisten' duplicates the title and name and is the only real waste.

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?

For a simple, non-destructive list tool with no output schema and no required parameters, the definition covers gating, ordering, and the primary filter. Only pagination behavior and what a payment record contains are absent, which the schema partly compensates for.

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 100%, so all three parameters are already documented in the schema. The description restates the invoice_id filtering intent ('auf eine Rechnung einschränken') but adds nothing about limit/offset pagination semantics, so the baseline 3 applies.

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 clear verb+resource ('Zahlungseingänge auflisten', 'Erfasste Zahlungseingänge') and adds scope: newest first, filterable by invoice. It does not explicitly contrast itself with list_invoices or amend_payment, so sibling differentiation is left to the resource name alone.

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?

The plan prerequisite is stated explicitly ('ab Business, darunter antwortet die API mit plan_required'), which is genuinely useful gating information. However, there is no guidance on when to choose this over listing invoices or other payment-related siblings, so usage is only implied.

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