Skip to main content
Glama
Sign In

Essentially Amsterdam

by com.essentiallyamsterdam
OverviewDiscussionsAdmin

Dutch rent points calculator (WWS)

rent_points
Read-onlyIdempotent

Dutch rent points (WWS, independent homes) and the maximum legal basic rent, as on our rent points calculator: total, sector, maximum rent and points per category. Every input is optional; defaults are the page example. Example: rooms=[{area_m2:24},{area_m2:11}].

Input Schema

NameRequiredDescriptionDefault
bathsNoBaths (default 0)
roomsNoRooms (living room, bedrooms, kitchen, bathroom...) with their floor area in m2; heated defaults to true. Default: the page example 24, 11, 7 and 4 m2.
showersNoShowers (default 1)
home_typeNoapartment (homes above or below it, default) or house (single-family)
woz_valueNoWOZ value in EUR (page default 400000)
build_yearNoBuild year, when energy_source is "year" (no valid label)
energy_indexNoEnergy index (EI), when energy_source is "ei"
energy_labelNoEnergy label A++++ to G (default C)
other_spacesNoOther spaces (storage, attic, utility room) with area in m2; heated defaults to false. Default: one 4 m2 storage.
cooling_roomsNoRooms with fixed cooling that also heats: 0, 1 or 2 (2 or more)
energy_sourceNolabel (default), ei (energy index) or year (no valid label: build year)
protected_statusNonone (default), national_monument, municipal_or_provincial_monument or protected_townscape_pre_1965
shared_outdoor_m2NoShared outdoor space in m2 (default 0)
kitchen_appliancesNoBuilt-in kitchen extras present. Default: extractor_hood, fridge, electric_oven, single_lever_tap.
kitchen_countertopNoCountertop length incl. sink and hob: under_1m, 1_to_2m or 2m_or_more (default)
private_outdoor_m2NoPrivate outdoor space in m2: garden, balcony, roof terrace (default 0)
washbasins_bathroomNoWashbasins in the bathroom (default 1)
toilets_separate_roomNoToilets in a separate toilet room (default 1)
shared_outdoor_addressesNoNumber of addresses sharing it (default 1)
newly_built_after_july_2024NoFirst lived in after 1 July 2024, construction started before 2028 (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changed
    • removedInput schema / properties / bath_plus_shower
      Removed value: -{
-  "description": "Bath plus separate shower in one bathroom (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / bathroom_cupboard
      Removed value: -{
-  "description": "Cupboard space in the bathroom of at least 40 by 40 cm (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / bathroom_meets_extras_requirements
      Removed value: -{
-  "description": "The bathroom meets the requirements for extras (default true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / bathroom_single_lever_taps
      Removed value: -{
-  "description": "Single-lever mixer taps in the bathroom (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / bathroom_sockets
      Removed value: -{
-  "description": "Bathroom sockets, max 2 per washbasin (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / bathroom_thermostatic_taps
      Removed value: -{
-  "description": "Thermostatic mixer taps in the bathroom (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / bubble_baths
      Removed value: -{
-  "description": "Bubble baths (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / double_washbasins_bathroom
      Removed value: -{
-  "description": "Double washbasins in the bathroom (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / double_washbasins_other
      Removed value: -{
-  "description": "Other rooms or spaces with a double washbasin (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / energy_performance_fee
      Removed value: -{
-  "description": "An energy performance fee (EPV) is agreed (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / extra_cupboard_units
      Removed value: -{
-  "description": "Extra kitchen cupboard units above the minimum, per 60 cm (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / heated_hallways
      Removed value: -{
-  "description": "Heated hallways and landings (page default 1)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / heated_open_kitchen
      Removed value: -{
-  "description": "There is a heated open kitchen (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / kitchen_basic_level
      Removed value: -{
-  "description": "The kitchen meets the basic level (default true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / new_build_2015_2019
      Removed value: -{
-  "description": "New-build completed 2015 to 2019 (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / official_check_extra_points
      Removed value: -{
-  "description": "Points from the official Rent Check for anything not covered (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / shower_enclosures
      Removed value: -{
-  "description": "Fixed full shower enclosures (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / small_home_2018_2022
      Removed value: -{
-  "description": "Under 40 m2, completed 2018 to 2022, COROP Amsterdam or Utrecht (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / toilets_in_bathroom
      Removed value: -{
-  "description": "Toilets in the bathroom (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / towel_radiators
      Removed value: -{
-  "description": "Towel radiators (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / vanity_units
      Removed value: -{
-  "description": "Built-in vanity units with washbasin (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / video_door_entry
      Removed value: -{
-  "description": "Video and audio door entry (default false)",
-  "type": "boolean"
-}
    • removedInput schema / properties / wall_hung_bathroom
      Removed value: -{
-  "description": "Of the bathroom toilets, wall-hung (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / wall_hung_separate
      Removed value: -{
-  "description": "Of the separate toilets, wall-hung (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / washbasins_other
      Removed value: -{
-  "description": "Other rooms or spaces with a washbasin (default 0)",
-  "maximum": 100000000,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / woz_valuation_date
      Removed value: -{
-  "description": "2025 (the WOZ letter of 2026, default), 2024, or none_use_legal_minimum",
-  "enum": [
-    "2024",
-    "2025",
-    "none_use_legal_minimum"
-  ],
-  "type": "string"
-}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds that defaults mirror the calculator page rather than zero/null and enumerates the returned fields, which is useful since there is no output schema; however, it gives no detail on units, rounding, or how sector thresholds are applied.

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?

Three short sentences, front-loaded with what the tool computes before the defaults caveat and the example. The phrase 'as on our rent points calculator' is slightly redundant with the title, but nothing else is wasted.

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 20-parameter, all-optional calculator with a fully documented schema and no output schema, the description covers the two things the schema cannot: default behavior on omission and the shape of the returned result. Missing only minor operational detail such as the currency/period of the maximum rent.

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 per-parameter definitions are already carried by the schema and a baseline of 3 applies. The description goes beyond that by clarifying that all 20 parameters are optional and that omission means page-example defaults, and it supplies a concrete nested-array example (rooms=[{area_m2:24},{area_m2:11}]) that illustrates the object shape.

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 domain artifact (Dutch rent points / WWS for independent homes) and states what is produced: total, sector, maximum legal basic rent, and points per category. The verb is only implicit ('calculate'), but the resource and output are unambiguous, and no sibling tool in the list overlaps with this domain.

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?

It tells the agent that every input is optional and that omitted inputs fall back to the page-example defaults, which is real usage guidance for a 20-parameter tool with zero required params. It does not say when a caller should prefer this over other approaches or what preconditions exist (e.g., only for independent homes, not rooms), leaving scope only partially implied.

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

All Essentially Amsterdam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources