Skip to main content
Glama

opplevagent-mcp

by io.github.slookisen
OverviewDiscussionsAdmin

Request a gårdssalg booking (pending — email confirmation required)

book_gardssalg

Submit a booking REQUEST for a Norwegian gårdssalg (farm-sale) producer discovered via discover_gardssalg. Send inn en reservasjonsforespørsel for et gårdssalg-besøk. IMPORTANT: this NEVER creates a confirmed booking — it creates a PENDING request, exactly like the producer's own website form. The PRODUCER reviews the request and responds (confirms, proposes another time, or declines); guest_email only receives a read-only status link, never anything that can finalize the booking. No payment is involved (pickup/visit, pay on arrival, as today). Only producers with an active booking status (see discover_gardssalg's booking.live field) can be booked — a paused/not-yet-onboarded producer is rejected with a clear message, never a silent failure. VIKTIG: oppretter ALDRI en bekreftet booking — kun en avventende forespørsel; produsenten mottar forespørselen og svarer (bekrefter, foreslår nytt tidspunkt eller avslår). ONE-SENTENCE FLOW («book et møte hos X fredag 20. oktober kl. 10 for 4 personer»): call this ONCE with provider_query='X' (the producer's name — no discover_gardssalg round-trip needed), slot_at, party_size, guest_name, guest_email and requested_weekday='fredag'. The tool resolves X to exactly one producer (or returns candidates / not-found with NO booking created), checks that the date really is a Friday (or returns weekday_mismatch:true with the nearest Fridays, NO booking created), then submits the request and notifies the producer by email. guest_name and guest_email are the HUMAN guest's own — ask the guest for them if you do not have them; never invent or reuse someone else's. Required: provider_id OR provider_query, slot_at (requested date/time, 'YYYY-MM-DDTHH:MM' Europe/Oslo), party_size, guest_name, guest_email. Optional: requested_weekday, experience_id, guest_phone, notes, confirm_outside_hours. The requested slot_at is ALWAYS hard-rejected if it's in the past or too far ahead. If the producer has stated opening hours and slot_at falls outside them, this returns outside_hours:true (not an error) instead of creating the booking — retry once with confirm_outside_hours:true if the exact requested time should be kept anyway. On success the response carries the resolved producer (provider.navn) and slot_at_local (e.g. 'fredag 23. oktober 2026 kl. 10:00') — read both back to the guest. Example: provider_query 'Fjordgard Bryggeri', slot_at '2026-10-23T10:00', requested_weekday 'fredag', party_size 4, guest_name 'Kari Nordmann', guest_email 'kari@example.no'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional free-text note to the producer (e.g. dietary needs, arrival details).
slot_atYesRequested visit date/time, local (Europe/Oslo), format 'YYYY-MM-DDTHH:MM'. Example: '2026-08-15T13:00'. This is a REQUEST — the producer may confirm, suggest another time, or decline.
guest_nameYesFull name of the person the reservation is for. Example: 'Kari Nordmann'
party_sizeYesNumber of people in the group (1-50). Example: 4
guest_emailYesGuest's email address — REQUIRED. Receives a confirmation-of-request email plus a read-only status link; the booking stays pending until the PRODUCER responds (confirms, proposes another time, or declines) — the guest's link cannot finalize anything. Example: 'kari@example.no'
guest_phoneNoOptional guest phone number.
provider_idNoThe gårdssalg producer's id — the `id` field of a discover_gardssalg result (NOT the profile slug). Example: '3f1b2c4d-...'. Either provider_id or provider_query is required; provider_id wins when both are given.
experience_idNoOptional experience UUID if this booking is for a specific listed experience rather than a general gårdssalg visit.
provider_queryNoAlternative to provider_id: the producer's name as the guest said it, optionally with a place, e.g. 'Fjordgard Bryggeri' or 'Egge gård Steinkjer'. Resolved to exactly ONE producer; if several match, the tool returns the candidates (no booking created) so you can ask the guest which one; if none match, it says so.
requested_weekdayNoSafety check — the weekday the guest actually said, e.g. 'fredag' or 'Friday'. If slot_at does not fall on that weekday (Europe/Oslo) the tool returns weekday_mismatch:true with the nearest dates that do, instead of booking the wrong day. Always pass it when the guest named a weekday.
confirm_outside_hoursNoSet to true only when RETRYING after a previous call to this tool returned outside_hours:true and the requested time should be kept anyway, despite falling outside the producer's stated opening hours. Omit on a first attempt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / provider_id / description
      Previous value: -"The gårdssalg producer's id, from a discover_gardssalg result (NOT the profile slug). Example: '3f1b2c4d-...'"New value: +"The gårdssalg producer's id — the `id` field of a discover_gardssalg result (NOT the profile slug). Example: '3f1b2c4d-...'. Either provider_id or provider_query is required; provider_id wins when both are given."
    • addedInput schema / properties / provider_query
      Added value: +{
+  "description": "Alternative to provider_id: the producer's name as the guest said it, optionally with a place, e.g. 'Fjordgard Bryggeri' or 'Egge gård Steinkjer'. Resolved to exactly ONE producer; if several match, the tool returns the candidates (no booking created) so you can ask the guest which one; if none match, it says so.",
+  "maxLength": 200,
+  "type": "string"
+}
    • addedInput schema / properties / requested_weekday
      Added value: +{
+  "description": "Safety check — the weekday the guest actually said, e.g. 'fredag' or 'Friday'. If slot_at does not fall on that weekday (Europe/Oslo) the tool returns weekday_mismatch:true with the nearest dates that do, instead of booking the wrong day. Always pass it when the guest named a weekday.",
+  "maxLength": 20,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "provider_id",
-  "slot_at",
-  "party_size",
-  "guest_name",
-  "guest_email"
-]New value: +[
+  "slot_at",
+  "party_size",
+  "guest_name",
+  "guest_email"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / confirm_outside_hours
      Added value: +{
+  "description": "Set to true only when RETRYING after a previous call to this tool returned outside_hours:true and the requested time should be kept anyway, despite falling outside the producer's stated opening hours. Omit on a first attempt.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

The annotations only provide basic flags, but the description discloses substantial behavior: it never finalizes a booking, the producer must respond, guest_email only receives a read-only status link, provider_query resolution can return candidates without booking, and various validations return flags like weekday_mismatch and outside_hours. This far exceeds what the annotations 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?

The description is long but front-loaded with the most critical caveat ('NEVER creates a confirmed booking') and structured around an example flow. The bilingual repetition and repeated emphasis on the pending nature are somewhat redundant, making it slightly less concise than ideal while remaining scannable and useful.

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 complex state-changing tool with no output schema, the description covers the success response fields (provider.navn and slot_at_local), all major failure and edge-case paths, required versus optional parameters, validation behavior, and a complete example. An agent has everything needed to invoke it correctly and to handle the outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even with 100% schema coverage, the description adds significant meaning: provider_query is explained as a replacement for a discover round-trip, confirm_outside_hours is scoped to retry-only usage, and guest_name/guest_email are stressed as belonging to the actual human guest. It also explains hard rejection rules for slot_at that are not in 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?

The description opens with a specific verb and resource—'Submit a booking REQUEST for a Norwegian gårdssalg producer'—and immediately separates this from a confirmed booking by emphasizing it creates only a PENDING request. This makes the tool's purpose unmistakable and distinguishes it from discovery-only sibling tools.

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?

It explicitly instructs 'call this ONCE', provides a concrete one-sentence flow with a full example, and states clear when-not-to-proceed conditions such as inactive producers, past/too-far slot_at, weekday mismatches, and outside-hours behavior. It also references discover_gardssalg's booking.live field and how to retry with confirm_outside_hours, so an agent knows exactly when and how to use it.

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