Skip to main content
Glama

Request a visit or tasting at a drink producer (pending until the producer replies)

book_gardssalg
Destructive

Use this to request a visit or tasting (besøk, smaking) at a Norwegian gårdssalg drink producer found with discover_gardssalg or named by the guest; it sends a visit request and does not sell or order products. 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) and creates no 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'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slot_at": "<slot_at>",
      "party_size": "<party_size>",
      "guest_name": "<guest_name>",
      "guest_email": "<guest_email>"
    },
    "name": "book_gardssalg"
  }
}

Input 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?

Annotations only say readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true; the description adds far more: the request stays PENDING, the producer (not the guest) decides, the email link is read-only, no payment occurs, past/too-far-ahead slots are hard-rejected, and paused producers are rejected with a clear message rather than silently. It also discloses response signals (outside_hours:true, weekday_mismatch:true) that the agent must handle.

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 critical constraint (never a confirmed booking, only a pending request) is front-loaded and the text is chunked into scannable blocks (IMPORTANT, ONE-SENTENCE FLOW, Required/Optional, Example). It is nonetheless long, and the Norwegian sentences restate the English IMPORTANT block almost verbatim, which is redundancy rather than new information for an agent.

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 an 11-parameter mutation tool with no output schema, the description covers what the agent needs: prerequisites (active booking.live status), failure modes (candidates, not-found, weekday_mismatch, outside_hours, past/future rejection), and the two success fields to read back to the guest (provider.navn, slot_at_local). Nothing material is missing.

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?

Although schema coverage is already 100%, the description adds resolution semantics the schema cannot: provider_query resolves to exactly one producer or returns candidates/not-found with no booking, requested_weekday acts as a guard against booking the wrong day, and confirm_outside_hours is only for a retry after outside_hours:true. It also clarifies slot_at format and the ownership requirement for guest_name/guest_email.

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 — requesting a visit/tasting booking at a Norwegian gårdssalg producer — and immediately draws the boundary against siblings and adjacent actions: producers are found with discover_gardssalg, and the tool 'does not sell or order products'. The title and description together make it unmistakable versus discover_gardssalg/discover_experiences.

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?

Gives explicit when-to-use (guest named a producer or a booking intent exists), an alternative path (provider_query instead of a discover_gardssalg round-trip), and a worked one-sentence flow. It also documents the retry carve-out for confirm_outside_hours and the 'ask the guest for guest_name/guest_email; never invent' rule, so no decision is left to inference.

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.