Skip to main content
Glama

statischeberekening.nl geodata

Building data (BAG, 3DBAG)

pand
Read-onlyIdempotent

Look up a Dutch building by address or BAG id: construction year and use (BAG), measured roof height, ridge and eaves height, roof shape and pitch, footprint dimensions (3DBAG), neighbours, listed monument. Give one: adres or bag_id. Missing data is 'niet vastgesteld'. Answers in Dutch.

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

Input Schema

NameRequiredDescriptionDefault
adresNoDutch address: street, house number and town (or postcode and house number)
bag_idNoBAG building id (pand), 16 digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description is free to add the non-obvious behaviour: missing values come back as 'niet vastgesteld' and all answers are in Dutch. That is real context an agent needs to interpret output, though it says nothing about failure modes (no match, ambiguous address, both params supplied).

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?

Four short sentences, front-loaded with the action, then the input rule, then two output conventions. Every sentence carries distinct information; no restatement of the title or name.

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 no output schema, the description compensates by listing the returned attributes and the null-value convention, which is the right allocation of space for a 2-param read tool. Remaining gaps are minor: no guidance on what happens when neither or both parameters are given, and no note on match ambiguity.

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, but the description adds a constraint the schema does not encode: only one of adres or bag_id should be supplied (the schema has zero required fields and no oneOf). It does not, however, describe address formatting nuances beyond what the parameter descriptions already state.

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 verb and resource ('Look up a Dutch building by address or BAG id') and then enumerates exactly which attributes are returned (construction year, roof heights, footprint, neighbours, monument status). The domain is unmistakable and cannot be confused with the sibling tools grond, wind, or how_to.

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?

'Give one: adres or bag_id' tells the agent how to select an input, and the field list implies when the tool is the right one (need for building attributes). There is no explicit when-not or alternative routing, but no sibling covers building lookups, so nothing important is left ambiguous.

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