Skip to main content
Glama

Zakelijke kilometers

record_mileage

Book business kilometres driven in a private car at the fixed per-kilometre rate for Dutch sole proprietor tax records; excludes company cars and commuting.

Instructions

Book business kilometres driven with the owner’s private car at the fixed rate per kilometre. Not for a company car, and not for commuting to an employer.

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": {
      "date": "<date>",
      "km": "<km>",
      "description": "<description>"
    },
    "name": "record_mileage"
  }
}

Input Schema

NameRequiredDescriptionDefault
kmYes
dateYesCalendar date, YYYY-MM-DD
descriptionYesFrom, to and purpose

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already disclose a non-read-only, non-destructive, closed-world mutation, and the description adds the important constraint that only private-car business driving qualifies. It does not say what is returned, whether the fixed rate is applied automatically or configurable, or how the entry interacts with VAT/books.

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?

Two short clauses, front-loaded with the primary action and followed immediately by the exclusions. No filler or redundant restatement of the title.

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 simple three-parameter booking tool with annotations covering safety and no output schema, the description supplies the essential scope and rate model. The main remaining gap is what happens after booking, which the absence of an output schema makes less critical.

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 67%, with only the date and description fields annotated; 'km' relies on its bounds and the description's mention of a per-kilometre rate. The description adds context for km but nothing about date formatting or what the description field should contain, leaving a modest gap.

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 gives a specific verb ('Book') and resource ('business kilometres driven with the owner's private car'), plus the pricing basis ('fixed rate per kilometre'). It is clearly distinguishable from expense, invoice, and receipt tools by naming the exact scenario it covers.

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?

It explicitly states two exclusions — company cars and commuting to an employer — which is strong when-not guidance. It stops short of naming a sibling alternative for those excluded cases, so the agent must infer where to route them.

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