Skip to main content
Glama

opplevagent-mcp

by io.github.slookisen
OverviewDiscussionsAdmin

Discover Norwegian farm-sale drink producers (gårdssalg)

discover_gardssalg
Read-onlyIdempotent

Search opplevagent.no's gårdssalg (farm-sale) vertical — Brreg-registered Norwegian drink producers (bryggeri/cideri/vingård/destilleri/gårdskafé/mjød/seltzeri) selling directly from the farm. Finn norske gårdssalg-produsenter (drikkeprodusenter som selger direkte fra gården) etter fylke, kommune og produsenttype. / Filter by county (fylke), municipality (kommune), and producer type. Also supports near-me search via lat/lng (+ optional radius_km): when given, results include a rounded distance_km and are sorted nearest-first, and rows with no geocoded location are excluded (never a fabricated distance). Returns id (the provider_id for book_gardssalg), name, location, producer type, and an honest booking status (live direct booking vs. a dark-launch 'coming soon' note — never overclaims booking availability). To look up ONE specific producer by name (e.g. when the guest says 'book hos Fjordgard Bryggeri'), pass query. Examples: 'gårdssalg i Vestland', 'cideri near lat 60.4 / lng 5.3', 'bryggeri med booking', query: 'Fjordgard Bryggeri'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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ø)
fylkeNoNorwegian county (fylke) of the producer. Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland'
limitNoMax results (default 20, max 50)
queryNoFree-text lookup of a specific producer by name and/or place, e.g. 'Fjordgard Bryggeri', 'Egge gård', 'sideri Hardanger'. Every word must match the producer's name, URL slug, place (poststed) or municipality; exact name matches rank first. Use this to get the `id` (provider_id) for book_gardssalg when the guest names a producer.
kommuneNoNorwegian municipality (kommune) of the producer. Examples: 'Tromsø', 'Bergen', 'Stavanger'
radius_kmNoMax distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50
booking_liveNoWhen true, only return producers that currently accept direct bookings. Omit to include producers regardless of booking status.
producer_typeNoType of drink producer — one of the six canonical drink venue kinds: 'bryggeri' (brewery), 'cideri' (cidery), 'vingård' (winery), 'destilleri' (distillery), 'gårdskafé' (farm café), 'mjød'/'mjøderi' (meadery). 'seltzeri' also occurs in the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / producer_type / description
      Previous value: -"Type of drink producer. Examples: 'bryggeri' (brewery), 'cideri' (cidery), 'vingård' (vineyard), 'destilleri' (distillery), 'mjøderi' (meadery), 'seltzeri'"New value: +"Type of drink producer — one of the six canonical drink venue kinds: 'bryggeri' (brewery), 'cideri' (cidery), 'vingård' (winery), 'destilleri' (distillery), 'gårdskafé' (farm café), 'mjød'/'mjøderi' (meadery). 'seltzeri' also occurs in the data."
  2. Changed1 schema field changed
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Free-text lookup of a specific producer by name and/or place, e.g. 'Fjordgard Bryggeri', 'Egge gård', 'sideri Hardanger'. Every word must match the producer's name, URL slug, place (poststed) or municipality; exact name matches rank first. Use this to get the `id` (provider_id) for book_gardssalg when the guest names a producer.",
+  "maxLength": 200,
+  "type": "string"
+}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive. The description adds substantial behavioral nuance beyond that: results get a rounded distance_km and are nearest-first; rows without geocoded locations are excluded; distances are never fabricated; booking status is disclosed honestly; and only Brreg-registered producers are returned. This is exactly the kind of unobservable behavior an agent needs to know.

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 longer than average but information-dense, front-loading the tool's purpose and including a bilingual restatement that may help multilingual agents. The examples at the end concretely illustrate usage. It could be slightly tightened by merging the Norwegian and English sentences, but every sentence contributes meaningful guidance.

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?

Given 9 parameters, no required params, no output schema, and a rich set of behavioral caveats, the description is remarkably complete: it covers filtering, near-me behavior, sort order, exclusions, return fields, booking-status semantics, and how to use the result in a sibling tool. Nothing an agent needs to correctly invoke this tool 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?

The input schema has 100% coverage with individual parameter descriptions, so the baseline is 3. The description adds extra meaning by explaining that query is for retrieving the id needed by book_gardssalg, that radius_km only applies when lat/lng are present, and that booking_live filters the returned list. This goes beyond the schema without duplicating it.

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 states a specific verb ('Search') and resource ('opplevagent.no's gårdssalg vertical') and enumerates exactly what kinds of producers are covered. It clearly differentiates from siblings by explicitly mentioning that the returned id is the provider_id for book_gardssalg, and by framing itself as a discovery tool rather than an experience or booking tool.

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?

It gives concrete guidance on when to use query for a named producer ('when the guest names a producer') and when to use lat/lng for near-me search. It also explains filter dimensions (fylke, kommune, producer_type) and booking_live. However, it does not explicitly contrast with discover_experiences or state when NOT to use this tool, so it stops short of full alternative-selection guidance.

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