Skip to main content
Glama

Belastingregels

get_tax_rules
Read-only

Fetch the Dutch tax rules and rates Bookiz uses for a specific year—btw, KOR, deductions, KIA, kilometre rate, and brackets—each with its official source quote.

Instructions

The Dutch tax figures Bookiz calculates with for a year (btw rates, KOR limit, zelfstandigenaftrek, MKB-winstvrijstelling, KIA table, kilometre rate, income tax brackets), each with its official source. Pass key for one rule including the literal quote from the source page.

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

Input Schema

NameRequiredDescriptionDefault
keyNo
yearNo

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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by stating that each figure carries its official source and that a keyed lookup returns the literal quote from the source page, but it says nothing about pagination, response shape, or what happens when key is omitted.

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?

A single front-loaded sentence states the resource, followed by the parenthetical enumeration that makes the scope concrete, then one sentence on the keyed lookup. Dense but every clause carries information; the long parenthetical is the only mild density cost.

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 two-parameter read tool with no output schema, the description covers what is returned and what key adds. It leaves gaps an agent would want filled: whether key is optional, what a key looks like, and whether omitting year defaults to the current year.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it does explain both: year means the tax year the figures apply to, and key selects one rule and returns its source quote. It stops short of describing the key naming convention or the default all-rules behavior when key is omitted.

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?

The description names the specific resource (Dutch tax figures Bookiz calculates with for a year) and enumerates the concrete rule types returned (btw rates, KOR limit, zelfstandigenaftrek, MKB-winstvrijstelling, KIA table, kilometre rate, income tax brackets). That is enough for an agent to tell this apart from siblings like vat_return or year_report, which compute or report rather than expose constants.

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 only implied: the agent can infer this is the lookup to call for official tax constants, and that passing a key narrows to one rule with its source quote. There is no explicit when-to-use or when-not-to-use statement, and no guidance on whether this should be consulted before vat_return or year_report.

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