Skip to main content
Glama

Dutch address facts (free)

nl_home_basic
Read-onlyIdempotent

Free. Use when the user mentions a Dutch address or asks about a home in the Netherlands: year built, floor area, use, neighbourhood residents and average home value, liveability percentile, in English. Accepts postcode + house number or free text. Sources: BAG, CBS, Leefbaarometer.

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

Input Schema

NameRequiredDescriptionDefault
qNoAlternative to postcode: free-text address, e.g. 'Visschersplein 1 Utrecht'
additionNoOptional house number addition
postcodeNoDutch postcode, e.g. 3511LX
house_letterNoOptional house letter, e.g. A
house_numberNoHouse number, e.g. 1

Output Schema

NameRequiredDescriptionDefault
sourceNoSources to cite
addressNoThe address found
see_urlNoFactline page for this address
buildingNoYear built, floor area and use from BAG
liveabilityNoLeefbaarometer score
neighbourhoodNoResidents and average home value from CBS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "address": {
      +      "description": "The address found"
      +    },
      +    "building": {
      +      "description": "Year built, floor area and use from BAG"
      +    },
      +    "liveability": {
      +      "description": "Leefbaarometer score"
      +    },
      +    "neighbourhood": {
      +      "description": "Residents and average home value from CBS"
      +    },
      +    "see_url": {
      +      "description": "Factline page for this address"
      +    },
      +    "source": {
      +      "description": "Sources to cite"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds value beyond them: the data provenance (BAG, CBS, Leefbaarometer), that the payload is English, and that cost is zero — all things the schema and annotations do not convey.

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?

Front-loaded cost and trigger, then capabilities, then accepted input shapes, then sources. Four short sentences with no filler and nothing repeated from the schema.

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 an output schema present the description needn't describe return values, and 100% parameter coverage means inputs are handled. The only missing piece is explicit routing to the fuller paid report sibling when the basic facts are insufficient.

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 the baseline is 3; the description goes further by explaining the two input modes — postcode + house number versus free text — which clarifies the q/addition/house_letter relationship the schema only lists separately.

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?

Specific verb-and-resource framing with an explicit enumeration of the facts returned (year built, floor area, use, residents, average home value, liveability percentile) plus the data sources. It clearly is a free basic address-facts lookup, though it does not name a sibling to differentiate from (e.g. nl_home_report or nl_address_lookup).

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?

"Use when the user mentions a Dutch address or asks about a home in the Netherlands" gives a clear triggering condition. The word "Free" and the tier naming imply the paid report tools are the escalation path, but no exclusion or explicit alternative is stated.

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.

Resources