Skip to main content
Glama

statischeberekening.nl geodata

Wind zone and terrain category (NEN-EN 1991-1-4 NB)

wind
Read-onlyIdempotent

Wind zone (I, II, III) and a terrain category proposal (0, II, III) for a Dutch location under the Dutch National Annex of EN 1991-1-4, with the measured building height for an address. Give one: adres, postcode, x_rd + y_rd, or lat + lon. 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": "wind"
  }
}

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)
postcodeNoDutch postcode, e.g. 7511 AA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that output is in Dutch and that the terrain category is a 'proposal' (an estimate rather than a determination), which is a useful nuance, but says nothing about failure modes, precision, or how the measured building height is sourced.

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?

Three short sentences, front-loaded with the returned values, followed by the input rule and the language note. The phrase 'with the measured building height for an address' is slightly garbled and could be tightened, but nothing is padded.

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?

There is no output schema, yet the description enumerates the returned values (wind zone, terrain category, building height) and the response language, and it covers the one-of input rule. Combined with annotations that carry the safety and open-world profile, an agent has what it needs to call this correctly.

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; however the description adds a constraint the schema does not encode — that exactly one of adres, postcode, x_rd+y_rd, or lat+lon must be given (the schema has no oneOf and no required fields). That is meaningful guidance beyond the structured data.

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?

The description names a specific output (wind zone I/II/III plus a terrain category 0/II/III) computed for a Dutch location under a named standard (NEN-EN 1991-1-4 NB), and mentions the building height that comes back with it. It does not differentiate itself from the siblings (grond, how_to, pand), but the resource and standard are unambiguous.

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

Usage Guidelines3/5

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

The line 'Give one: adres, postcode, x_rd + y_rd, or lat + lon' is real invocation guidance about which input combination to supply. There is no statement of when this tool is preferred over another, no prerequisites, and no when-not condition, so usage is only implied by the domain.

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