nor-data/nve-mcp
Server 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hent_flomaktsomhetA | Sjekk om et koordinat (WGS84) ligger i NVE sitt flom-aktsomhetsområde (landsdekkende GIS-analyse) og i detaljert kartlagt flomsone (200-årsflom) der slik finnes. Returnerer også om punktet er innenfor analysert/kartlagt område, slik at 'ingen treff' kan skilles fra 'ikke kartlagt'. Kilde: NVE (kart.nve.no), åpne data. |
| hent_skredaktsomhetA | Sjekk om et koordinat (WGS84) ligger i NVE sine skred-aktsomhetsområder: snø-/steinskred, jord-/flomskred og kvikkleire (faregradssoner). Returnerer treff per skredtype med dekodet skredtype og kartleggingsstatus, slik at 'ingen treff' kan skilles fra 'ikke kartlagt'. Kilde: NVE/NGU (kart.nve.no), åpne data. |
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 address entirely different hazard types (flood vs landslide), with no overlap in their functionality. Clear distinction.
Both tools follow the same 'hent_' + hazard type pattern, using snake_case and Norwegian, providing a predictable naming convention.
With only 2 tools, the server is very narrow in scope. However, this may be appropriate for a focused hazard query service, though it feels slightly thin.
The server covers the two main hazard queries (flood and landslide) but lacks other potential hazard types (e.g., storm surge, wildfire) and has no data manipulation tools. Adequate for its stated purpose but not comprehensive.