Skip to main content
Glama

statischeberekening.nl geodata

Soil data (BRO, GeoTOP)

grond
Read-onlyIdempotent

Look up the soil at a Dutch location: nearest BRO cone penetration tests (CPT) with distance and date, the layer summary of the nearest, groundwater (GHG/GLG), GeoTOP, soil map. Give one: adres, x_rd + y_rd, or lat + lon. Indicative. 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": "grond"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude
lonNoWGS84 longitude
x_rdNoRD New (EPSG:28992) x in m
y_rdNoRD New (EPSG:28992) y in m
adresNoDutch address: street, house number and town (or postcode and house number)

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 declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely non-structured context: geographic scope limited to the Netherlands, 'Indicative' data-quality caveat, and 'Answers in Dutch' output language. It does not mention coverage limits of the underlying datasets (e.g. GeoTOP depth/extent) or response size, which keeps it short of a 5.

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?

Front-loaded with the resource and the returned datasets, then the input rule, then two short caveats ('Indicative. Answers in Dutch.') — no filler. The telegraphic style ('Give one:', bare 'adres, x_rd + y_rd, or lat + lon') is dense but still parseable; a slightly more explicit phrasing of the exclusivity would cost nothing and gain clarity.

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 correctly carries the burden of explaining return values, and it enumerates the datasets returned plus their language and indicative nature. For a five-parameter open-world lookup with no required fields, the main residual gap is how the address form is resolved and whether partial coordinate pairs are rejected — minor next to what is already stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not encode: the schema sets no required fields and no mutual exclusion, whereas the description states that exactly one locator form must be given (address, or the x_rd/y_rd pair, or the lat/lon pair). That constraint is essential for correct invocation and is absent from the structured data.

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?

A specific verb ('look up') and resource ('the soil at a Dutch location'), followed by an enumeration of exactly what comes back: nearest BRO CPTs with distance and date, layer summary, GHG/GLG groundwater, GeoTOP and soil map. An agent can predict the payload without opening the schema, and the domain (Dutch subsurface) is unambiguous against siblings like pand or wind.

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?

It gives a concrete input constraint — 'Give one: adres, x_rd + y_rd, or lat + lon' — which tells the agent exactly which of the mutually exclusive locator forms to supply, plus the caveat 'Indicative' to set expectations on precision. There is no explicit when-not-to-use guidance or named alternative, but the sibling set is unrelated domains, so the omission is minor.

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