Skip to main content
Glama

Jaaroverzicht

year_report
Read-only

Generate an annual profit-and-loss report and taxable profit calculation for a Dutch sole proprietor, including deductions, income tax and Zvw reserve estimates for the income tax return.

Instructions

Profit and loss for a year and the steps to taxable profit: omzet, kosten per category, afschrijvingen, kleinschaligheidsinvesteringsaftrek, zelfstandigenaftrek, startersaftrek, MKB-winstvrijstelling, plus an indication of income tax and Zvw to set aside. These are the figures for "winst uit onderneming" in the aangifte inkomstenbelasting.

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

Input Schema

NameRequiredDescriptionDefault
yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 value by disclosing the report's contents and its intended downstream use (reserving for income tax and Zvw), but says nothing about how the year is interpreted, what happens if the year param is omitted, or whether figures are final or provisional.

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?

Two sentences, purpose front-loaded, no filler. The second sentence about aangifte inkomstenbelasting earns its place by establishing use context. The long Dutch jargon list is dense but functional since it enumerates the returned components.

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 read-only report with no output schema, the enumerated line items effectively serve as a return-value preview, which is a genuine strength. What is missing is the default behavior of the optional year param and any note on currency or period granularity, leaving a small but real gap for an agent deciding how to invoke it.

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% for the single 'year' parameter, and the description does not compensate: it only says 'for a year' without stating what a missing value defaults to (the parameter is optional), whether historical years are allowed, or whether the year is calendar or fiscal. This is a case where the description needed to pick up the schema's slack and did not.

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 opens with a concrete verb and resource ('Profit and loss for a year and the steps to taxable profit') and enumerates the exact line items included (omzet, kosten per category, afschrijvingen, the various aftrekposten, MKB-winstvrijstelling, plus income tax and Zvw). That is enough to tell it apart from the tax-rules and overview siblings by content, though it never names those siblings explicitly.

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 context is implied by the closing clause: these are the figures needed for 'winst uit onderneming' in the aangifte inkomstenbelasting, so an agent can infer it belongs at tax-filing time. There is no explicit when-not guidance, no mention of when to prefer get_overview or get_tax_rules, and no prerequisites stated.

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