Skip to main content
Glama

Find experiences, tastings and producer visits in Norway

discover_experiences
Read-onlyIdempotent

Search Opplevagent's published catalogue of experiences in Norway, including food and drink tastings and producer visits (smaking, besøk hos drikkeprodusenter). Filtrer på fylke (county), kategori, vær, sesong, innendørs/utendørs, gruppestørrelse, pris og varighet. / Filter by county, category, weather, season, indoor/outdoor, group size, price, and duration. Also supports near-me search via lat/lng (+ optional radius_km): when given, results include a rounded distance_km and a geo_precision flag ('address' = exact, 'kommune' = approximate municipality centroid) and are sorted nearest-first. Returns title, category, location (fylke/kommune), description, and booking URL if available. Only verified experiences from active providers (Brreg-checked) are returned. Covers Norway only: pass the user's request in query; for a place outside Norway (e.g. Kenya) the tool returns no experiences, and the answer is that Opplevagent only covers Norway. Food-product shopping such as buying stockfish is outside this tool's scope. Pass that intent in query; an out_of_scope response must not be retried as a general discovery search. Examples: 'hva kan vi finne på i Troms om vinteren?' (fylke='Troms', season='winter'), 'wildlife experiences' (category='dyreliv_safari'), 'outdoor activities in Oslo for 4 people', 'experiences within 50km of lat 69.65 / lng 18.95'.

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": "discover_experiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge of the youngest participant. Filters out experiences with a minimum-age requirement above this. Example: 8
latNoOrigin latitude for a near-me search (decimal degrees). Must be given together with lng. Example: 69.65 (Tromsø)
lngNoOrigin longitude for a near-me search (decimal degrees). Must be given together with lat. Example: 18.95 (Tromsø)
sortNo'distance' — sort results ascending by distance from lat/lng. Already the default whenever lat/lng are given; this makes the request explicit.
fylkeNoNorwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland'
limitNoMax results (default 20, max 50)
queryNoThe user's request in a few words, including any place they named — e.g. 'safari lodge in Kenya', 'northern lights in Tromsø'. Opplevagent only covers Norway: when this names a place outside Norway and no Norwegian fylke/kommune or coordinates are given, the tool returns no experiences and says so. Include the purchase intent too: buying stockfish is food retail, not an experience search.
seasonNoSeason filter: 'summer', 'winter', 'spring' or 'autumn' (the Norwegian words sommer/vinter/vår/høst work too). Year-round experiences are always included. Use this (not category or weather) when the user asks what to do in a season, e.g. 'Troms om vinteren' → fylke='Troms', season='winter'.
kommuneNoNorwegian municipality (kommune). Examples: 'Tromsø', 'Bergen', 'Stavanger'
weatherNoToday's weather, not the season: 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'. For 'in winter' use season instead.
categoryNoExperience category slug — one of: 'kultur_historie' (culture/history, museums), 'natur_friluft' (nature/outdoors), 'adrenalin_action', 'sightseeing_transport' (sightseeing, cruises, cable cars), 'overnatting_opplevelse' (stays), 'dyreliv_safari' (wildlife, whale/moose safaris, dog sledding), 'vinter_sno' (winter & snow), 'mat_drikke' (food & drink), 'velvaere_spa' (wellness/spa). Call list_experience_categories for live counts. Omit category for a general 'what can we do' question. 'In winter' / 'om vinteren' is a season, not a category: use season='winter' — 'vinter_sno' covers only snow activities and would hide e.g. northern-lights cruises.
languageNoRequired language for the experience. Examples: 'no', 'en'
max_priceNoMaximum price per person in Norwegian kroner (NOK). Example: 500
radius_kmNoMax distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50
group_sizeNoNumber of people in the group. Used to filter experiences by min/max group capacity. Example: 4
duration_maxNoMaximum duration in minutes. Example: 120 (2 hours)
indoor_outdoorNoIndoor/outdoor preference. Examples: 'indoor', 'outdoor', 'both'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The user's request in a few words, including any place they named — e.g. 'safari lodge in Kenya', 'northern lights in Tromsø'. Opplevagent only covers Norway: when this names a place outside Norway and no Norwegian fylke/kommune or coordinates are given, the tool returns no experiences and says so."New value: +"The user's request in a few words, including any place they named — e.g. 'safari lodge in Kenya', 'northern lights in Tromsø'. Opplevagent only covers Norway: when this names a place outside Norway and no Norwegian fylke/kommune or coordinates are given, the tool returns no experiences and says so. Include the purchase intent too: buying stockfish is food retail, not an experience search."
  2. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "The user's request in a few words, including any place they named — e.g. 'safari lodge in Kenya', 'northern lights in Tromsø'. Opplevagent only covers Norway: when this names a place outside Norway and no Norwegian fylke/kommune or coordinates are given, the tool returns no experiences and says so.",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Experience category slug — one of: 'kultur_historie' (culture/history, museums), 'natur_friluft' (nature/outdoors), 'adrenalin_action', 'sightseeing_transport' (sightseeing, cruises, cable cars), 'overnatting_opplevelse' (stays), 'dyreliv_safari' (wildlife, whale/moose safaris, dog sledding), 'vinter_sno' (winter & snow), 'mat_drikke' (food & drink), 'velvaere_spa' (wellness/spa). Call list_experience_categories for live counts."New value: +"Experience category slug — one of: 'kultur_historie' (culture/history, museums), 'natur_friluft' (nature/outdoors), 'adrenalin_action', 'sightseeing_transport' (sightseeing, cruises, cable cars), 'overnatting_opplevelse' (stays), 'dyreliv_safari' (wildlife, whale/moose safaris, dog sledding), 'vinter_sno' (winter & snow), 'mat_drikke' (food & drink), 'velvaere_spa' (wellness/spa). Call list_experience_categories for live counts. Omit category for a general 'what can we do' question. 'In winter' / 'om vinteren' is a season, not a category: use season='winter' — 'vinter_sno' covers only snow activities and would hide e.g. northern-lights cruises."
    • changedInput schema / properties / season / description
      Previous value: -"Season filter: 'summer', 'winter', 'spring' or 'autumn' (the Norwegian words sommer/vinter/vår/høst work too). Year-round experiences are always included."New value: +"Season filter: 'summer', 'winter', 'spring' or 'autumn' (the Norwegian words sommer/vinter/vår/høst work too). Year-round experiences are always included. Use this (not category or weather) when the user asks what to do in a season, e.g. 'Troms om vinteren' → fylke='Troms', season='winter'."
    • changedInput schema / properties / weather / description
      Previous value: -"Weather suitability filter. 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'"New value: +"Today's weather, not the season: 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'. For 'in winter' use season instead."
  4. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Experience category slug. Examples: 'natur_friluft', 'dyreliv_safari', 'mat_drikke', 'vinter'"New value: +"Experience category slug — one of: 'kultur_historie' (culture/history, museums), 'natur_friluft' (nature/outdoors), 'adrenalin_action', 'sightseeing_transport' (sightseeing, cruises, cable cars), 'overnatting_opplevelse' (stays), 'dyreliv_safari' (wildlife, whale/moose safaris, dog sledding), 'vinter_sno' (winter & snow), 'mat_drikke' (food & drink), 'velvaere_spa' (wellness/spa). Call list_experience_categories for live counts."
    • changedInput schema / properties / season / description
      Previous value: -"Season filter. Examples: 'summer', 'winter', 'spring', 'autumn'"New value: +"Season filter: 'summer', 'winter', 'spring' or 'autumn' (the Norwegian words sommer/vinter/vår/høst work too). Year-round experiences are always included."
  5. Changed4 schema fields changed
    • addedInput schema / properties / lat
      Added value: +{
      +  "description": "Origin latitude for a near-me search (decimal degrees). Must be given together with lng. Example: 69.65 (Tromsø)",
      +  "maximum": 90,
      +  "minimum": -90,
      +  "type": "number"
      +}
    • addedInput schema / properties / lng
      Added value: +{
      +  "description": "Origin longitude for a near-me search (decimal degrees). Must be given together with lat. Example: 18.95 (Tromsø)",
      +  "maximum": 180,
      +  "minimum": -180,
      +  "type": "number"
      +}
    • addedInput schema / properties / radius_km
      Added value: +{
      +  "description": "Max distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50",
      +  "exclusiveMinimum": 0,
      +  "maximum": 5000,
      +  "type": "number"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "'distance' — sort results ascending by distance from lat/lng. Already the default whenever lat/lng are given; this makes the request explicit.",
      +  "enum": [
      +    "distance"
      +  ],
      +  "type": "string"
      +}
  6. Added
  7. Removed
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent/closed-world annotations, the description discloses verified-provider-only results (Brreg-checked), that near-me results carry a rounded distance_km and a geo_precision flag with 'address' vs 'kommune' meaning, nearest-first ordering, and the return fields. These are behavioral traits the annotations cannot convey.

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?

Front-loaded with purpose and scope, then filters, then near-me mechanics, then boundaries and examples — a sensible order. It is on the long side and the Norwegian/English filter enumeration plus the stockfish out-of-scope note repeat content that also appears in the `query` and `season` schema descriptions.

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?

For a 17-parameter, zero-required tool with no output schema, the description covers the return shape (title, category, location, description, booking URL), geo-precision semantics, data-quality gating, and hard scope limits. Nothing an agent needs in order to call it correctly or interpret a null result is missing.

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, but the description adds cross-parameter meaning: lat/lng must travel together with optional radius_km and implies distance sorting, and it shows example mappings ('hva kan vi finne på i Troms om vinteren?' → fylke='Troms', season='winter'). It does not restate every parameter, which is appropriate given the schema.

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?

States a specific verb and resource with scope: 'Search Opplevagent's published catalogue of experiences in Norway, including food and drink tastings and producer visits.' It also delimits scope against non-experience intents (food retail/stockfish) and against non-Norwegian places, so an agent can tell it apart from a general discovery search 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 Guidelines5/5

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

Explicit routing rules are given: use lat/lng (+radius_km) for near-me, pass non-Norwegian or out-of-scope intent through `query`, and do not retry an out_of_scope response as general discovery. Worked examples map natural-language requests to concrete filters, which is exactly the when-to-use guidance an agent needs.

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.