Skip to main content
Glama

Nl Schools Near Postcode

nl_schools_near_postcode
Read-onlyIdempotent

The nearest primary and secondary schools to a Dutch postcode, with name, address, denomination, pupil count, website, distance in km, and the latest end-of-primary test results (reading and maths share reaching target vs the national share) or secondary exam pass rates, from the national education register. Example: {"postcode":"1011AB"} -> OBS IJplein 0.68 km, De Witte Olifant 0.84 km, ... Returns source and data_as_of (latest register update date among the schools).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "1011AB"
    },
    "name": "nl_schools_near_postcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesDutch postcode, 4 digits + 2 letters, e.g. "1011AB"

Output Schema

NameRequiredDescriptionDefault
townNo
foundNo
sourceNo
cite_asNo
primaryNo
postcodeNo
secondaryNo
data_as_ofNo
primary_countNo
secondary_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint true and destructiveHint false, so the safety profile needs no restating. The description adds real value beyond that: the national education register as source, a 'source' and 'data_as_of' freshness field, and an example result showing distance-ordered output. It doesn't cover failure behavior for malformed postcodes or any result-count/radius cap, 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?

The core purpose and returned fields lead the sentence, with the example input/output and provenance note at the end. It is dense and largely front-loaded, though the long comma-separated field list and the example snippet partly duplicate what the output schema already supplies.

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?

For a single-parameter read tool with a full schema, a rich annotations block and an output schema, the description covers what the tool is, where the data comes from and how fresh it is. The remaining gaps are minor: how many schools are returned, the search radius, and behavior on invalid or non-existent postcodes.

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?

There is a single parameter at 100% schema description coverage, so the schema already defines the 4-digits-plus-2-letters format. The description repeats the format only implicitly through the example '{"postcode":"1011AB"}', adding no semantics the schema lacks. Baseline 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 names a specific verb+resource ('nearest primary and secondary schools to a Dutch postcode') and enumerates the returned fields (name, address, denomination, pupil count, website, distance, test/exam results), so an agent can distinguish it from unrelated siblings like nl_address_facts without opening the schema.

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?

Usage is only implied: the tool clearly takes a Dutch postcode and returns nearby schools, but the description never states when to prefer it over other options or any exclusions (e.g. non-Dutch postcodes, invalid formats). No alternative tool is named, and none of the listed siblings appear to overlap, so the omission is low-risk but leaves guidance at the implied level.

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.