io.github.woonstadrotterdam/monumenten
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_verblijfsobject_idA | Get verblijfsobject ID using address. Use postal_code + house_number OR street + house_number + city. Additional filters like house_letter and house_suffix can be provided for more precise matching. |
| get_monumental_statusA | Get the monumental status of a verblijfsobject. Always mention the source for the Rijksmonument status if it is a Rijksmonument. (RCE = Rijksdienst voor het Cultureel Erfgoed.) Reply in the user's language. provinciaal_monument is not looked up. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one resolves an address to a verblijfsobject ID, and the other retrieves monumental status for a verblijfsobject. There is no overlap or ambiguity between them.
Both tools follow a consistent get_<object>_<attribute> pattern, though the second tool's name (get_verblijfsobject_id) describes the return value rather than the resource attribute, which is a minor deviation.
Two tools is on the thin side for a server, but the narrow domain (looking up monumental status by address) makes the count defensible. It is borderline but not unreasonable.
The two tools form a complete workflow: address → verblijfsobject ID → monumental status. However, there is no direct lookup by verblijfsobject ID, no monument details endpoint, and no support for provinciaal monument lookups, leaving some gaps.