datanorge
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 |
|---|---|
| search_datasetsA | Search data.norge.no (the Norwegian national data catalogue) for datasets by keyword or topic. Returns matching datasets with their id, publisher, themes and a short description. Norwegian search terms usually match best. Use a returned id with get_dataset to get download links. |
| get_datasetA | Fetch full metadata for one dataset by its id (from search_datasets), including every distribution with its download/access URL, format and licence. This is how you find where to actually get the data. |
| search_apisB | Search data.norge.no for APIs / data services — live endpoints serving Norwegian public data (e.g. Statistics Norway, Kartverket, Brønnøysundregistrene). Use get_api with a returned id for endpoint URLs. |
| get_apiA | Fetch full metadata for one API / data service by its id (from search_apis), including its endpoint URL(s) and a link to the machine-readable description (e.g. OpenAPI spec). |
| fetch_dataA | Download the actual data from a distribution's downloadURL or accessURL (from get_dataset), an API endpoint (from get_api), or any http(s) data URL. Returns the content for text formats (CSV, JSON, XML, GeoJSON); large responses are truncated and binary content returns metadata only. Use this to retrieve the data itself, not just its catalogue metadata. |
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 5 tools
Each tool has a clearly distinct purpose: search for datasets vs search for APIs, retrieve metadata for each, and fetch actual data. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., fetch_data, get_api, search_datasets), using lowercase with underscores. No mixing of conventions.
Five tools is an appropriate scope for a data catalogue server, covering search, metadata retrieval, and data download without being excessive or too minimal.
The core operations for accessing public data are covered: search both datasets and APIs, retrieve full metadata, and download data. Minor gaps like browsing by theme or listing all catalogs are not critical but would be nice additions.