Skip to main content
Glama

Horseback: zajęcia na Jurze

Szczegóły zajęć

get_activity_details
Read-onlyIdempotent

Use this when the user asks about one specific Horseback activity, camp or event: what it is, programme, for whom and from what age, how long, where, group size, what to bring, FAQ, price and how to sign up. Returns everything the activity page says, the matching price-list rows and the page link. Get the id from get_activities (field id). Do not guess the id - get it from get_activities. noUpcomingDate means there is currently no date - say so and suggest asking about the next one. Present only the programme, variants and prices returned by the tools; do not add elements (e.g. first aid, meals, custom vouchers).

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": {
      "activity": "<activity>"
    },
    "name": "get_activity_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityYesActivity id from get_activities, e.g. "spotkanie-z-koniem" or "oboz-jezdziecki-dzieci-mlodziez".
languageNoLanguage of the returned texts: "pl" (Polish, default) or "en" (English). Use the language of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this a safe read (readOnly, idempotent, not destructive, closed-world), so the description does not need to repeat that. It adds real behavioral context: what the response contains (page content, matching price-list rows, page link), the noUpcomingDate edge case, and a constraint against inventing elements such as meals or custom vouchers. That goes well beyond the annotations.

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 purpose and its sub-questions lead, followed by return shape, id provenance, edge case, and presentation rules, so an agent can stop reading early. The id instruction is stated twice ("Get the id from get_activities" and "Do not guess the id - get it from get_activities"), which is mild redundancy rather than bloat.

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?

There is no output schema, so the description must explain the return; it does so concretely (page content, price-list rows, link) and also covers the empty case. For a two-parameter read tool with full annotation coverage, nothing an agent needs in order to call it correctly 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 both parameters, including the two enums, are already documented and form the baseline of 3. The description adds provenance the schema cannot express: the activity id must be taken from get_activities rather than composed. It adds little on the language parameter beyond the schema's "use the language of the conversation".

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 names the exact resource and scope ("one specific Horseback activity, camp or event") and enumerates the facets it covers: programme, age range, duration, location, group size, packing, FAQ, price, sign-up. It also separates this tool from get_activities, which supplies the id, so an agent can choose between them without opening either 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?

It states exactly when to use the tool (a question about one specific activity) and routes the agent to get_activities for the id, twice warning against guessing it. It also gives guidance for the noUpcomingDate case, telling the agent to say there is no date and suggest asking about the next one.

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