Skip to main content
Glama

Uitgave laten vervallen

void_expense
Destructive

Cancel a mistakenly booked expense while keeping it visible with a reason; blocked once its btw period has been filed.

Instructions

Cancel an expense that was booked by mistake. It stays visible with the reason. Not possible once its btw period has been filed.

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": {
      "ref": "<ref>",
      "reason": "<reason>"
    },
    "name": "void_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: despite destructiveHint=true, the expense is not erased but remains visible carrying the stored reason, and the operation is blocked after VAT filing. These are behavioral facts an agent cannot infer from the annotation flags. It does not say whether the void is reversible or what response/error comes back, which keeps 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 short sentences; the action is front-loaded and each following sentence adds a distinct constraint (visibility of the reason, VAT-filing cutoff). No filler.

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 two-parameter mutation with no output schema, purpose and preconditions are covered adequately. What is missing is identification of the ref parameter and any note on the failure mode when the period is filed, so an agent must guess at input formatting.

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 coverage is 0%, so the description must carry parameter meaning and largely does not. 'It stays visible with the reason' implicitly explains that reason is persisted and shown, which is useful, but ref is never explained (expense id? number? UUID?). With two required, undocumented parameters this is a significant gap.

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 specific verb+resource (

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?

Gives a clear when: an expense booked by mistake. And a clear when-not: once the btw (VAT) period has been filed. It names no alternative tool, but no sibling appears to overlap the void operation, so the guidance is sufficient for selection.

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