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. A county name in the query (e.g. 'Vestland') is applied as the fylke filter; for a whole county, prefer fylke.
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 / query / description
      Previous value: -"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."New value: +"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. A county name in the query (e.g. 'Vestland') is applied as the fylke filter; for a whole county, prefer fylke."
  2. 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."
  3. 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"
+}
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent annotations: states near-me results are sorted nearest-first with a rounded distance_km, that ungeocoded rows are excluded with 'never a fabricated distance', and that booking status is honest rather than overclaimed. These are non-obvious traits that materially affect interpretation of results.

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 the core purpose and mode examples, and every section earns its place. However the Norwegian and English restatements of the same filter sentence plus a long trailing example list make it longer than strictly necessary.

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?

With no output schema, the description compensates by naming the returned fields (id/provider_id, name, location, producer type, booking status) and explaining the geocoding caveat. Nothing an agent needs to call it correctly or interpret results 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 semantics: lat/lng must be given together, radius only bites when lat/lng are present, and a county name inside `query` is applied as the fylke filter. It mostly restates schema detail for query ranking, keeping it short of a 5.

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?

Names a specific verb and resource ('Search opplevagent.no's gårdssalg vertical — Brreg-registered Norwegian drink producers') and enumerates the exact producer kinds covered. It is immediately distinguishable from book_gardssalg (booking) and discover_experiences (other verticals).

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?

Explicitly routes: use `query` to look up ONE producer by name and to obtain the id for book_gardssalg; use `fylke` for a whole county; use lat/lng for near-me. Concrete examples of each mode are given, so the agent knows when to pick which input path.

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