Skip to main content
Glama

Nl Address Facts

nl_address_facts
Read-onlyIdempotent

Facts about any Dutch address, in English, from official registers: year built, building age, floor area, use (residential/retail/...), BAG ids, coordinates, municipality, province, neighbourhood name and code, neighbourhood residents/households/average home value (WOZ)/owner-occupied share, the Leefbaarometer liveability percentile, energy label where registered, and municipality house-price trend. Input is postcode + house number (+ optional letter/addition). Example: {"postcode":"1012JS","house_number":1} -> Dam 1, Amsterdam, built 1914, 23,820 m2 retail, neighbourhood Oude Kerk e.o. Unresolvable addresses return found:false with a reason. Returns source and data_as_of (year of the neighbourhood and liveability figures).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "1012JS",
      "house_number": 1
    },
    "name": "nl_address_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
additionNoOptional number addition, e.g. "2" or "BIS"
postcodeYesDutch postcode, 4 digits + 2 letters, e.g. "1012JS" (a space is fine)
house_letterNoOptional house letter, e.g. "A"
house_numberYesHouse number, e.g. 1

Output Schema

NameRequiredDescriptionDefault
foundNo
queryNo
sourceNo
addressNo
cite_asNo
buildingNo
data_as_ofNo
liveabilityNo
energy_labelNo
neighbourhoodNo
municipality_house_pricesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered; the description still adds meaningful context the annotations cannot: data provenance (official registers), output language (English), explicit failure semantics (found:false with a reason), and the meaning of the returned data_as_of field. It stops short of describing rate limits, coverage completeness, or what happens when a postcode is valid but the house number is not.

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 clause and input shape are front-loaded, and the trailing example, failure case, and data_as_of note each carry useful information. The long mid-sentence enumeration of every returned field is the weakest part, since much of it duplicates the output schema and pads the description.

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 annotations covering safety, a 100%-covered input schema, and an output schema documenting the response, the description supplies the remaining essentials: provenance, English output, failure behaviour, and the temporal meaning of data_as_of. Minor gaps remain around coverage scope (all Dutch addresses?) and which registers back the figures, but nothing an agent needs to call it correctly is missing.

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 100%, so all four parameters (postcode, house_number, house_letter, addition) are already documented in the schema, making 3 the baseline. The description's summary of the input shape and its worked example add light confirmation but no semantics beyond what the schema states, such as how house_letter and addition interact or which format the postcode normalises to.

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 resource ('Facts about any Dutch address ... from official registers') and enumerates the fields returned, so the agent knows exactly what class of data this yields, distinct from company_facts or nl_vehicle_by_plate by virtue of the postcode+house_number domain. The concrete example (Dam 1, Amsterdam) removes any remaining ambiguity about the unit of lookup.

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 implied through the required input shape ('Input is postcode + house number (+ optional letter/addition)') and the failure case ('Unresolvable addresses return found:false with a reason'). However, there is no explicit when-to-use or when-not guidance, and no sibling alternative is named, so the agent must infer that this is the address-level lookup rather than the near-postcode or school tools.

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.