Skip to main content
Glama

Horseback: zajęcia na Jurze

Wstępna rezerwacja

create_prereservation

Use this when the user wants to book, reserve a place, sign up a child or children, or book for a group for one specific Horseback event or group activity from the lists in eventId / productId (eventId = the id of an event page in get_activities; productId = "/" from get_activities). It sends the same pre-reservation as the "Wstępna rezerwacja" form on the activity page: no payment is taken, nothing is confirmed yet - Horseback calls or texts the user to confirm the date and details. Before calling, collect from the user: (1) a phone number; (2) for an event (eventId): the number of children and their ages (childrenInfo; for adult events, the number of participants), and the variant (eventVariant) when the event has more than one; for a group activity (productId): the number of people and the age of the group (groupInfo); (3) consent: ask the user directly whether they agree that Horseback contacts them by phone or SMS about this reservation, and pass consent: true only after they said yes. Send one call per event or activity. Do not include other personal data (names, health information). Do not use for payment, for activities not in the lists, or without the user's explicit consent. It does not confirm a date. Data controller: Horseback Sp. z o.o.; privacy policy: https://horseback.pl/polityka-prywatnosci (English: https://horseback.pl/polityka-prywatnosci?lang=en). Variants: warsztaty-rozwojowe-z-konmi-dla-kobiet: "Warsztaty jednodniowe" or "Warsztaty dwudniowe (z noclegiem i wyżywieniem)"; sylwester-jezdziecki: "Grupa starsza (10:00-12:30)" or "Grupa młodsza (11:30-13:30)".

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": {
      "phone": "<phone>",
      "consent": "<consent>"
    },
    "name": "create_prereservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesPhone number of the user: 9 digits (Polish number, e.g. "601 234 567") or international format with + (e.g. "+48601234567", "+4915112345678").
consentYestrue only after the user explicitly agreed that Horseback contacts them by phone or SMS about this reservation.
eventIdNoEvent id (event page slug). Give either eventId or productId, not both.
languageNoLanguage of the returned texts: "pl" (Polish, default) or "en" (English). Use the language of the conversation.
groupInfoNoGroup activities (productId) only, required: number of people and the age of the group, e.g. "15 people, adults".
productIdNoGroup activity id "<category>/<slug>". Give either eventId or productId, not both.
childrenInfoNoEvents only, required: number of children and their ages, e.g. "2 children: 7 and 10 years old" (adult events: number of participants).
eventVariantNoEvents with more than one variant only, required there: the variant name exactly as listed in this tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / eventId / enum
      Previous value: -[
      -  "warsztaty-rozwojowe-z-konmi-dla-kobiet",
      -  "mikolajki-jezdzieckie",
      -  "sylwester-jezdziecki"
      -]New value: +[
      +  "warsztaty-rozwojowe-z-konmi-dla-kobiet",
      +  "andrzejki-jezdzieckie",
      +  "mikolajki-jezdzieckie",
      +  "sylwester-jezdziecki"
      +]
    • changedInput schema / properties / productId / enum
      Previous value: -[
      -  "konie/wycieczka-konska-przygoda-z-edukacja",
      -  "konie/warsztaty-zrozumiec-innosc",
      -  "konie/spotkanie-z-koniem",
      -  "konie/sesje-zdjeciowe-z-konmi",
      -  "konie/oboz-jezdziecki-dzieci-mlodziez",
      -  "konie/oboz-szkoleniowy-mlodziez",
      -  "gry-terenowe-i-turystyka/gra-terenowa-na-gore-zborow",
      -  "gry-terenowe-i-turystyka/podstawy-turystyki-pieszej",
      -  "samoobrona/samoobrona-zajecia-grupowe",
      -  "strzelectwo/podstawy-strzelectwa-zajecia-grupowe",
      -  "strzelectwo/integracja-na-strzelnicy-i-przejazdzki-hummerem",
      -  "miejski-detoks/miejski-detoks-jednodniowy",
      -  "miejski-detoks/miejski-detoks-weekendowy",
      -  "miejski-detoks/kapiel-lesna"
      -]New value: +[
      +  "konie/wycieczka-konska-przygoda-z-edukacja",
      +  "konie/warsztaty-zrozumiec-innosc",
      +  "konie/warsztaty-relaksacyjne-dla-rodzicow-jednodniowe",
      +  "konie/spotkanie-z-koniem",
      +  "konie/sesje-zdjeciowe-z-konmi",
      +  "konie/oboz-jezdziecki-dzieci-mlodziez",
      +  "konie/oboz-szkoleniowy-mlodziez",
      +  "gry-terenowe-i-turystyka/gra-terenowa-na-gore-zborow",
      +  "gry-terenowe-i-turystyka/podstawy-turystyki-pieszej",
      +  "samoobrona/samoobrona-zajecia-grupowe",
      +  "strzelectwo/podstawy-strzelectwa-zajecia-grupowe",
      +  "strzelectwo/integracja-na-strzelnicy-i-przejazdzki-hummerem",
      +  "miejski-detoks/miejski-detoks-jednodniowy",
      +  "miejski-detoks/miejski-detoks-weekendowy",
      +  "miejski-detoks/kapiel-lesna"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / productId / enum
      Previous value: -[
      -  "konie/wycieczka-konska-przygoda-z-edukacja",
      -  "konie/warsztaty-zrozumiec-innosc",
      -  "konie/spotkanie-z-koniem",
      -  "konie/sesje-zdjeciowe-z-konmi",
      -  "konie/oboz-jezdziecki-dzieci-mlodziez",
      -  "konie/oboz-szkoleniowy-mlodziez",
      -  "gry-terenowe-i-turystyka/gra-terenowa-na-gore-zborow",
      -  "samoobrona/samoobrona-zajecia-grupowe",
      -  "strzelectwo/podstawy-strzelectwa-zajecia-grupowe",
      -  "strzelectwo/integracja-na-strzelnicy-i-przejazdzki-hummerem",
      -  "miejski-detoks/miejski-detoks-jednodniowy",
      -  "miejski-detoks/miejski-detoks-weekendowy",
      -  "miejski-detoks/kapiel-lesna"
      -]New value: +[
      +  "konie/wycieczka-konska-przygoda-z-edukacja",
      +  "konie/warsztaty-zrozumiec-innosc",
      +  "konie/spotkanie-z-koniem",
      +  "konie/sesje-zdjeciowe-z-konmi",
      +  "konie/oboz-jezdziecki-dzieci-mlodziez",
      +  "konie/oboz-szkoleniowy-mlodziez",
      +  "gry-terenowe-i-turystyka/gra-terenowa-na-gore-zborow",
      +  "gry-terenowe-i-turystyka/podstawy-turystyki-pieszej",
      +  "samoobrona/samoobrona-zajecia-grupowe",
      +  "strzelectwo/podstawy-strzelectwa-zajecia-grupowe",
      +  "strzelectwo/integracja-na-strzelnicy-i-przejazdzki-hummerem",
      +  "miejski-detoks/miejski-detoks-jednodniowy",
      +  "miejski-detoks/miejski-detoks-weekendowy",
      +  "miejski-detoks/kapiel-lesna"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description layers on what annotations cannot convey: no payment is taken, nothing is confirmed, Horseback phones/texts the user, consent must be captured verbally first, and only phone/children/group data may be sent. The data-controller and privacy-policy lines are unusual but legitimate for a PII-submitting form. Minor gap: it never says what the call actually returns.

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?

Purpose is front-loaded in the first sentence and the pre-call checklist is numbered, which is easy to follow. The block is long, but the length is driven by the variant enumeration and exclusions, which are load-bearing; a bulleted layout would read slightly better than the dense mid-section.

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?

For an 8-parameter, no-output-schema mutation tool, it covers prerequisites, exclusions, data-handling rules and enum values thoroughly. The only missing piece is a sentence on what the agent should expect back and tell the user (e.g., a pending request awaiting contact), since there is no output schema to lean on.

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?

Schema coverage is 100%, yet the description still adds real meaning: it explains that eventVariant must match the names listed in the description and then enumerates those names per event (warsztaty-rozwojowe-z-konmi-dla-kobiet, sylwester-jezdziecki), which the schema cannot supply. It also clarifies conditional requirements (childrenInfo for events incl. adult-event participant counts, groupInfo for productId) and the either/or relationship between eventId and productId.

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 ("sends the same pre-reservation as the 'Wstępna rezerwacja' form") and pins the scope to one event (eventId) or one group activity (productId) from get_activities. It explicitly separates itself from payment tools and from the listing sibling, so an agent can route correctly without opening the schema.

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 both the trigger ("user wants to book, reserve a place, sign up a child...") and explicit exclusions ("Do not use for payment, for activities not in the lists, or without the user's explicit consent"), plus the precondition checklist that must be collected before calling. It even specifies one call per event/activity rather than batching.

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.

Resources