Skip to main content
Glama

Factuur crediteren

credit_invoice
Destructive

Reverse a final invoice with a credit factuur dated today to correct mistakes, then issue a new accurate invoice.

Instructions

Reverse a final invoice with a creditfactuur dated today. Use this for any mistake on a final invoice, then create a correct new one.

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

Input Schema

NameRequiredDescriptionDefault
numberYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating, destructive operation. The description adds that the creditfactuur is dated today and applies only to final invoices. However, it does not explain whether the original invoice remains visible, whether the reversal is reversible, what permissions are needed, or what side effects occur.

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?

The definition is two short sentences with no wasted wording. The key action and context are front-loaded, and the follow-up instruction is placed immediately after the primary use case.

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

Completeness2/5

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

For a destructive financial mutation with no output schema and 0% schema description coverage, the description is too sparse. An agent still lacks parameter guidance, permission requirements, success behavior, and details about how the original and credit invoices relate.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the two undocumented parameters. It implies that an invoice must be identified, but it never mentions the required number parameter, its expected format, or the optional reason parameter. The reason parameter is completely absent from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: reverse a final invoice by creating a creditfactuur dated today. It clearly distinguishes the reversal action from the follow-up act of creating a correct new invoice, so an agent can tell it apart from create_invoice or finalize_invoice.

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

Usage Guidelines4/5

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

It gives clear when-to-use guidance: any mistake on a final invoice. It also names the natural follow-up alternative, creating a correct new invoice. It does not explicitly state when not to use it, such as for draft invoices or already-credited invoices, so it falls short of full exclusion guidance.

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