Skip to main content
Glama

Betaling registreren

register_payment
Destructive

Marks a final invoice as paid on a selected date, defaulting to today. Set paid_on to null to undo an incorrect payment.

Instructions

Mark a final invoice as paid on a date (default today). Pass paid_on: null to undo a mistake.

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": {
      "number": "<number>"
    },
    "name": "register_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes
paid_onNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false and destructiveHint=true, so the agent knows this mutates state. The description adds genuinely new behavior: the date defaults to today and null reverts the payment. It does not say what else the payment affects (e.g. whether the invoice is locked afterwards or whether books/VAT entries change) or how to correct a wrong date other than past-date replacement.

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?

Two short sentences, action first, exception second. No filler and nothing redundant with the schema.

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 2-parameter mutation with no output schema this covers the essential action, the default, and the reversal. Gaps remain around the required `number` argument and preconditions/failure modes (non-final invoice, already-paid invoice), which matter for a destructiveHint=true tool.

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 0%, so the description carries the burden. It fully clarifies paid_on (default today, null = undo), which the schema's anyOf only hints at. However, the required `number` parameter is never explained — the agent must guess it is the invoice number rather than a payment or contact identifier.

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?

Specific verb plus resource: 'Mark a final invoice as paid on a date'. The qualifier 'final invoice' implicitly scopes it away from draft or credit invoices among the siblings, though no sibling is named for contrast.

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?

Usage is implied by the verb (record that an invoice has been paid) and the description supplies a concrete reverse path ('pass paid_on: null to undo a mistake'). It does not state preconditions such as whether the invoice must be finalized first, nor does it point to a sibling alternative for non-final invoices.

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