Skip to main content
Glama

MaxRechnung

Zahlungseingang abrufen

get_payment
Read-only

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

Zahlungseingang abrufen

Ein einzelner Zahlungseingang, auch ein stornierter (voided_at gesetzt). Business-Tarif.

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": {
      "id": "<id>"
    },
    "name": "get_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPfad-Parameter id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, so the safety profile is covered. The description adds context the annotations lack: a plan-level entitlement gate with the concrete failure mode `plan_required`, and the behavior that voided records are still returned rather than filtered out. It stops short of describing response shape or error surface beyond the plan code.

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?

The content is short but poorly front-loaded and redundant: the plan requirement appears twice ('Tarif: ab Business…' at the top and 'Business-Tarif.' at the end), and the title is restated as a standalone sentence in the middle. The core fact – single payment retrieval, voided included – is buried between the duplicated tier notes.

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?

For a simple one-parameter getter the description covers the key call-level facts (plan entitlement, voided records included). With no output schema, though, the agent gets no indication of what a payment object contains or what is returned in the `plan_required` case, leaving a gap the description could have filled.

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?

There is a single required UUID parameter at 100% schema description coverage, so the schema already documents it. The description adds no meaning about how `id` is obtained or how a voided payment's id differs. Baseline 3 applies when the schema does the heavy lifting.

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 a specific verb and resource: 'Zahlungseingang abrufen' / 'Ein einzelner Zahlungseingang' – retrieve a single payment. It also discloses the scope edge case that voided payments are included when `voided_at` is set. It does not explicitly differentiate itself from sibling getters (e.g. get_invoice), so it falls 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?

The useful precondition 'Tarif: ab Business (darunter antwortet die API mit plan_required)' tells the agent when the call will fail, which is real usage guidance. However, no alternative tool or situation is named (e.g. no pointer to a list/search counterpart or to amend_payment/cancel_payment for mutations), so usage context 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