Skip to main content
Glama

Tourist tax

tourist_tax
Read-onlyIdempotent

The tourist tax for one stay, worked out night by night: each tax that applies (regional and city parts separately), the amount or the range when the star rating or type of stay is not given, how many nights are charged, how it is paid, announced changes in force on those nights, and the official source and date for each. Accepts a researched place or any town; towns outside the researched places return researched=false. Percentage taxes need room_price_total. Residents', medical and other special exemptions are listed in rules, not applied.

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": {
      "place": "<place>",
      "check_in": "<check_in>",
      "nights": "<nights>"
    },
    "name": "tourist_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoArea/zone code where a place has zones (e.g. Venice)
townNoTown or municipality inside a region (e.g. 'Albufeira' in the Algarve)
placeYesA researched place ('Lisbon', 'Algarve', 'Paris') or any town ('Quarteira', 'Funchal', 'Kyoto')
roomsNoDefault 1 (for per-room taxes)
adultsNoDefault 2
nightsYesNumber of nights from check_in (1-60)
check_inYesYYYY-MM-DD
child_agesNoAge of each child on check-in, one entry per child (many taxes exempt under-12s, -16s or -18s); omit for none
type_of_stayNoHotel stars, apartment, holiday rental, etc.
adults_70_plusNoHow many of the adults are 70 or over
local_categoryNoThe authority's own category label, as returned in options
room_price_totalNoRoom price for the whole stay, for percentage taxes

Output Schema

NameRequiredDescriptionDefault
noteNo
pageNo
errorNo
taxesNo
totalNo
researchedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld=false) by disclosing fallback behavior: a range is returned when star rating or type of stay is not supplied, and out-of-scope towns return researched=false instead of failing. It also flags a parameter dependency (percentage taxes require room_price_total) and a scope limit (exemptions listed, not applied) — exactly the kind of behavior an agent would otherwise have to discover by trial.

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?

The purpose is front-loaded in the first clause and the remainder is a dense enumeration where each item corresponds to a real output dimension. The long comma-separated list is information-dense rather than padded, though it reads as one sprawling sentence and could be split for scanability.

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?

With 12 parameters, 100% schema coverage, full annotations and an output schema, the description covers the remaining gaps: parameter interdependency, fallback outputs, and out-of-scope handling. It is essentially complete for invocation; the enumeration of return fields slightly duplicates the output schema, which is harmless but not additive.

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 coverage is 100%, so baseline is 3; the description earns above that by explaining the semantic role of two parameters — room_price_total is required for percentage-based taxes, and type_of_stay/star rating determines whether a single amount or a range comes back. The place/town distinction and the researched=false outcome add meaning beyond the schema's own strings.

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?

States a specific computation ('the tourist tax for one stay, worked out night by night') and enumerates the exact outputs: regional and city parts separately, amount or range, nights charged, payment, announced changes, source and date. This clearly separates it from list_places (lookup) and place_rules (exemptions), which is confirmed by the description pointing exemptions to `rules`.

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 real context for when it is applicable: accepts a researched place or any town, and towns outside the researched set return researched=false. It also states the precondition 'Percentage taxes need room_price_total' and routes exemptions to `rules` rather than applying them. It stops short of an explicit 'use place_rules instead if...' routing statement, so it is a 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.