Dutch property report by address: build year, energy label, neighbourhood, monument, schools.
Scored across 1 tool
With only one tool, there is no possibility of confusing tools. The tool's purpose is clearly defined and distinct, and it does not overlap with any other tool because no other tools exist.
The single tool name, get_verified_property_context, follows a clear verb_noun pattern and is descriptive of its function. Since there is only one tool, there is no inconsistency in naming conventions.
The server's sole purpose is to provide verified property context for Dutch addresses, which is a narrow, read-only domain. A single comprehensive tool is the right scope and does not feel thin because it delivers a rich, multi-source response.
The tool covers a wide range of data points (BAG, CBS, RIVM, energy label, heritage, protected areas, schools, planning) and includes important handling for address match verification and provenance. For a context lookup service, there are no obvious missing capabilities; it fully addresses the stated purpose.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| depth | No | Hoeveel 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. | |
| address | Yes | Nederlands adres, bij voorkeur met plaatsnaam of postcode, bijvoorbeeld 'Grote Markt 2, Haarlem' of '2011RD 2'. Zonder plaatsnaam is het resultaat vaak dubbelzinnig. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavior. It thoroughly explains the output structure (blocks), the meaning of provenance and statuses (not_configured/unavailable means not retrieved, not nonexistent), and warns against making assumptions. It also reveals special behaviors like match_verified=false indicating a different property and match_ambiguous alternatives, which are critical for correct interpretation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is structured into clear paragraphs: overview and usage, response block structure, meaning of statuses and signals, critical caveats, and a disclaimer. Although relatively long, every sentence adds essential context and the most important usage guidance is front-loaded. This density is justified by the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having no output schema, the description sufficiently explains the return value structure and semantics via block names and detailed explanations. It covers edge cases (unmatched address, ambiguous candidates, unavailable data) and explicitly prohibits filling missing fields with estimates. This is complete guidance for correct selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters (address and depth) already described in detail within the input schema. The description does not add significant new parameter-level meaning beyond what the schema provides, though it integrates the address ambiguity warning into the broader narrative. Baseline 3 is appropriate since the schema handles parameter semantics adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with a specific verb 'Geeft' (provides) and clearly defines the resource: verified context of a Dutch residential address from official open sources. It distinguishes itself from potential sibling tools by listing concrete data categories (BAG, CBS, RIVM, energy label, heritage, schools) and explicitly stating when to use it (when someone asks about facts, risks, or surroundings of a Dutch address).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives an explicit when-to-use directive: 'Gebruik dit wanneer iemand vraagt naar feiten, risico's of omgeving van een Nederlands adres.' It also provides exclusions and cautions, such as stating this is not a valuation or legal/building advice, and clarifies how to handle ambiguous or unmatched addresses. Although no sibling alternatives are listed, the use case is precisely framed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get_verified_property_context1 field changedInput schema / properties / address / descriptionPrevious value: -"Nederlands adres, bij voorkeur met plaatsnaam of postcode, bijvoorbeeld 'Schoolstraat 1, Wassenaar' of '2242KE 1'. Zonder plaatsnaam is het resultaat vaak dubbelzinnig."New value: +"Nederlands adres, bij voorkeur met plaatsnaam of postcode, bijvoorbeeld 'Grote Markt 2, Haarlem' of '2011RD 2'. Zonder plaatsnaam is het resultaat vaak dubbelzinnig."get_verified_property_contextClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Dutch address dossier, vehicle, building, elevation, holidays, demographics. Free samples first.
A French address, all public facts: parcel, zoning, risks, permits, sales, energy labels. No key.
UK area & property intelligence for AI agents: reports, EPC, comparables, with source provenance.
French address intelligence: 18.6M sold prices, energy, risk, crime and schools — each sourced.
Add one secure layer between your agents and this server.
