Skip to main content
Glama

opplevagent-mcp

by io.github.slookisen
OverviewDiscussionsAdmin

Discover Norwegian experiences

discover_experiences
Read-onlyIdempotent

Search the opplevagent.no curated marketplace of Norwegian experiences and activities. 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. Examples: 'hva kan vi finne på i Troms om vinteren?', 'outdoor activities in Oslo for 4 people', 'experiences within 50km of lat 69.65 / lng 18.95'.

Input Schema

TableJSON 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)
seasonNoSeason filter. Examples: 'summer', 'winter', 'spring', 'autumn'
kommuneNoNorwegian municipality (kommune). Examples: 'Tromsø', 'Bergen', 'Stavanger'
weatherNoWeather suitability filter. 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'
categoryNoExperience category slug. Examples: 'natur_friluft', 'dyreliv_safari', 'mat_drikke', 'vinter'
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. 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"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds valuable behavioral details: results are verified (Brreg-checked), geo-precision flag, sorted nearest-first with lat/lng, and return fields. No contradictions.

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 description is reasonably concise and well-structured: purpose, filters, geo-features, return info, examples. The bilingual text adds length but is justified. Could be slightly tighter without losing clarity.

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?

Given no output schema, the description covers return fields (title, category, location, description, booking URL) and geo details. Missing pagination or error handling, but for a 16-parameter search tool it is fairly complete.

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?

Schema coverage is 100% with good descriptions for each parameter. The description adds little beyond summarizing filters and repeating constraints (e.g., radius_km applies only with lat/lng). Baseline 3 is appropriate as the description does not compensate for a coverage gap.

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 clearly states it searches the opplevagent.no marketplace, distinguishing it from siblings like get_experience (single item) and list_experience_categories (categories). The verb 'search' and resource are specific, and examples solidify purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description implies when to use (searching experiences with various filters) but does not explicitly state when not to use or point to specific alternatives like get_experience or list_experience_categories. However, the context is clear enough for inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All opplevagent-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources