Skip to main content
Glama

Dutch Property Context

Server Details

Dutch property report by address: build year, energy label, neighbourhood, monument, schools.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.6/5 across 1 of 1 tools scored.

Server CoherenceA
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is unequivocally distinct by default.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern ('get_' + descriptive noun phrase), which is consistent and predictable. With only one tool, there are no conflicting conventions.

Tool Count4/5

The server has just one tool, which is below the typical 3-15 range, but it is a comprehensive, non-trivial tool for a very narrow and focused domain. The count is slightly under but reasonable given the server's purpose.

Completeness5/5

The tool integrates data from multiple official sources (BAG, CBS, RIVM, energy label, heritage, protected areas, schools) and includes provenance and signals. For the stated purpose of retrieving verified property context, there are no obvious gaps; it is a complete read-only surface.

Available Tools

1 tool
get_verified_property_contextAInspect

Geeft de geverifieerde context van een Nederlands woonadres uit officiële open bronnen: BAG (bouwjaar, oppervlakte, gebruiksdoel), CBS-buurtcijfers, RIVM (omgevingsgeluid, PM2.5, NO2), het geregistreerde energielabel, rijksmonumentstatus, ligging in een beschermd stads- of dorpsgezicht, en nabije scholen. Gebruik dit wanneer iemand vraagt naar feiten, risico's of omgeving van een Nederlands adres.

Het antwoord heeft deze blokken: identity (welk pand is dit), building (bouwjaar, oppervlakte, gebruiksdoel), energy, location, neighbourhood (CBS), environment (geluid, PM2.5, NO2), heritage (rijksmonument), protected_area (beschermd stads- of dorpsgezicht, UNESCO-werelderfgoed), schools, planning, signals en provenance.

Die eerste blokken bevatten feiten uit een bron; provenance vertelt per bron welke, wanneer opgehaald en met welke status. signals zijn observaties die nadrukkelijk GEEN gebrek vaststellen: bouwjaar 1921 betekent niet dat er loden leidingen zijn, het betekent dat dat geverifieerd moet worden. Een status not_configured of unavailable betekent dat wij het niet hebben opgehaald, niet dat het niet bestaat — vul zulke velden nooit zelf in met een schatting.

Let in het bijzonder op identity.match_verified. Staat die op false, dan is het gevraagde adres niet teruggevonden en gaat de rest van het antwoord over een ander pand; meld dat dan aan de gebruiker in plaats van de gegevens te presenteren. Bij identity.match_ambiguous zijn er meerdere even goede kandidaten en staan die in match_alternatives.

Dit is geen taxatie en geen juridisch of bouwkundig advies.

ParametersJSON Schema
NameRequiredDescriptionDefault
depthNoHoeveel detail. 'compact' (standaard) laat de bron-URL's en de volledige scholenlijst weg en is ongeveer de helft kleiner; alle feiten en álle signalen zitten er gewoon in. Vraag 'full' alleen als je de complete scholenlijst of de exacte bron-URL's nodig hebt.
addressYesNederlands adres, bij voorkeur met plaatsnaam of postcode, bijvoorbeeld 'Schoolstraat 1, Wassenaar' of '2242KE 1'. Zonder plaatsnaam is het resultaat vaak dubbelzinnig.
Behavior5/5

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

The description thoroughly explains behaviors: signals are observations not deficits, statuses like 'not_configured' mean data wasn't retrieved, and identity.match_verified false indicates the address wasn't found and results refer to another property. It also includes a disclaimer that this is not tax or legal advice. Since there are no annotations, this full transparency is essential and well-provided.

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 description is longer than typical but well-structured into paragraphs covering purpose, output structure, and important semantic caveats. Each sentence provides useful information, avoiding redundancy. Slight verbosity prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there is no output schema, the description extensively explains the output format (blocks like identity, building, environment), the meaning of fields like match_verified, and the semantics of status values. It also covers usage context and caveats, making it highly complete.

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 coverage is 100% with detailed descriptions for both parameters. The tool description adds no additional parameter semantics beyond what is already in the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool's purpose: it gives verified context for a Dutch residential address from official sources, listing specific data types (BAG, CBS, RIVM, energy label, etc.). The verb 'geeft' (gives) and the specified resource make it unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: 'Gebruik dit wanneer iemand vraagt naar feiten, risico's of omgeving van een Nederlands adres.' It also provides guidance on using 'compact' vs 'full' depth, making the usage conditions clear.

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

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • F
    license
    -
    quality
    C
    maintenance
    UK property listing description generator. Give an AI assistant a postcode or address — it fetches comparable sales, EPC ratings, and Rightmove listings, then writes three copy variants ready for Rightmove, social media, and email.
    1
  • F
    license
    -
    quality
    D
    maintenance
    Property intelligence API for US real estate. Returns 16+ data points for any US address: noise levels, wetlands, slope, natural light, powerline proximity, crime rates, property facing direction, zoning, public record, radon risk, natural hazards (earthquake, flood, wildfire), neighborhood demographics, falling tree risk, RF/cell tower exposure, and nearby school.

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources