Skip to main content
Glama

Btw-aangifte

vat_return
Read-only

Prepares the Dutch btw-aangifte per rubriek for a chosen period with source documents, ICP list and deadline; defaults to the oldest unfiled period for copying into Mijn Belastingdienst.

Instructions

The btw-aangifte for a period (2026-Q4 or 2026-11), per rubriek in whole euros exactly as the form of Mijn Belastingdienst Zakelijk asks, with the documents behind every number, the ICP list and the deadline. Without a period it picks the oldest one that still has to be filed. The owner copies the figures into the form; Bookiz does not submit.

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

Input Schema

NameRequiredDescriptionDefault
periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: the no-period fallback selects the oldest unfiled period, figures are rounded to whole euros and mapped to form rubrieken, and critically that the tool does not submit anything. It stops short of saying what happens when no unfiled period exists (error vs. empty result).

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?

Front-loaded with the resource and its scope, then the output contents, the default behavior, and the non-submission caveat; every clause carries information. It is dense and somewhat comma-heavy, but no sentence is 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?

There is no output schema, so the description must characterize the return payload, and it does: per-rubriek euro amounts, the supporting documents, the ICP list and the deadline. What is missing for full completeness is the handoff state after calling it (how the figures get marked as filed) and the empty/no-period case.

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

Parameters4/5

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

With only one parameter and 0% schema description coverage, the description carries the burden and does well: it gives concrete accepted formats ('2026-Q4 or 2026-11') and explains the semantics of omitting the parameter entirely. Only the parameter name/optionality mechanics live in the schema, so this is a meaningful addition.

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 names a concrete resource (the Dutch btw-aangifte), the scope it covers (a period, per rubriek in whole euros in the exact Mijn Belastingdienst Zakelijk form layout), and what comes with it (underlying documents, ICP list, deadline). An agent can tell this is a prepare-VAT-return read operation rather than a filing or bookkeeping mutation.

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 rather than stated: it explains the default when no period is given ('picks the oldest one that still has to be filed') and that Bookiz does not submit, which hints a separate filing step exists. But it never names the obvious alternative in the sibling set (mark_vat_return_filed) or tells the agent when to prefer this over it, leaving the agent to infer the workflow.

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