Skip to main content
Glama

Btw-aangifte afsluiten

mark_vat_return_filed
Destructive

Records a submitted btw-aangifte for a period, freezing figures and locking the period only after filing is confirmed.

Instructions

Record that the owner filed the btw-aangifte for a period. This freezes the figures and locks the period. Only call after the owner confirms the filing was actually submitted.

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": {
      "period": "<period>"
    },
    "name": "mark_vat_return_filed"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYes
filed_onNoCalendar date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds substantive context the annotations cannot convey: the figures freeze and the period locks. That is exactly the consequence an agent needs to know before calling. It omits whether the action can be undone or what happens to downstream reports for that period.

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 with zero padding, and the action plus effect are front-loaded ahead of the precondition. Every sentence carries distinct information.

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?

For a two-parameter mutation with annotations and no output schema, the description covers the action, the irreversible-feeling consequence, and the confirmation gate. Remaining gaps are edge behavior such as re-filing or unfiling an already locked period.

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 description coverage is 50%: filed_on is documented in the schema, while period carries no schema description. The description references 'for a period' but adds no format, examples, or meaning beyond what the schema shows. Baseline 3 is right given partial coverage.

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 and resource: recording that the owner filed the btw-aangifte for a period. Clear enough to separate from a sibling like vat_return (which prepares/looks up the return), though it never names that sibling explicitly.

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 an explicit gating condition: only call after the owner confirms the filing was actually submitted. That is a real usage rule, not just context. It stops short of naming the alternative tool to use while the return is still being prepared.

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