Skip to main content
Glama

Horseback: zajęcia na Jurze

Zajęcia i usługi

get_activities
Read-onlyIdempotent

Use this when the user asks what Horseback offers or looks for activities at Horseback (categories: horse activities, hippotherapy, field games and hiking, city detox, self-defense, shooting). Do not use for events on specific dates (use get_upcoming_events) or for places other than Horseback. Returns categories with descriptions and the classes in each one (id, name, format, description, date if the class has one, link), the same as the /zajecia pages. Optionally only one category by its id. For the full page of one class call get_activity_details with its id. noUpcomingDate means the event currently has no date - say so and suggest asking about the next one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional category id; omit to get all categories.
languageNoLanguage of the returned texts: "pl" (Polish, default) or "en" (English). Use the language of the conversation.

Output Schema

NameRequiredDescriptionDefault
contactNoHorseback contact: phone, email, website, social profiles.
languageYesLanguage of the returned texts.
categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / categories / items / properties / activities / items / properties / noUpcomingDate / description
      Previous value: -"Present when the event has no future date (only past ones): tell the user there is currently no date and to ask Horseback about the next one."New value: +"Present when the event has no future date (only past ones): the notice shown on the event page. Tell the user there is currently no date and to ask Horseback about the next one."
  2. Changed1 schema field changed
    • addedOutput schema / properties / categories / items / properties / activities / items / properties / noUpcomingDate
      Added value: +{
      +  "description": "Present when the event has no future date (only past ones): tell the user there is currently no date and to ask Horseback about the next one.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "categories": {
      +      "items": {
      +        "properties": {
      +          "activities": {
      +            "items": {
      +              "properties": {
      +                "date": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "description": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "format": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "id": {
      +                  "type": "string"
      +                },
      +                "name": {
      +                  "type": "string"
      +                },
      +                "url": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "name",
      +                "url"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "activities"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "contact": {
      +      "description": "Horseback contact: phone, email, website, social profiles.",
      +      "type": "object"
      +    },
      +    "language": {
      +      "description": "Language of the returned texts.",
      +      "enum": [
      +        "pl",
      +        "en"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "language",
      +    "categories"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile needs no restating. The description adds genuinely new behavioral context: the returned structure per category and class, the equivalence to the /zajecia pages, and the noUpcomingDate edge case with an instruction to tell the user and suggest asking about the next date. It stops short of noting pagination or size limits, which keeps it from a 5.

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 usage trigger and exclusions, then the return shape, then the optional filter and next step — a sensible order with no filler sentences. The parenthetical field list (id, name, format, description, date, link) partially duplicates the output schema and is the one piece that doesn't fully earn its space.

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?

Given a read-only lookup with two enum params, an output schema, and full annotation coverage, the description supplies everything else an agent needs: trigger, exclusions, the sibling for the adjacent intent, the shape of the result, and the noUpcomingDate handling instruction. Nothing required for correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters are enums with documented values, so the schema carries the parameter burden. The description only echoes the optional single-category filter already documented in the schema and adds no new syntax or selection criteria, which is the baseline 3.

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 ('what Horseback offers', 'look for activities at Horseback') and enumerates the six categories covered. It explicitly separates itself from get_upcoming_events (dated events) and get_activity_details (single class), so an agent can pick the right tool without opening a 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 an explicit trigger ('when the user asks what Horseback offers'), two explicit exclusions with the sibling to use instead (get_upcoming_events, and places other than Horseback), and routes single-class requests to get_activity_details with its id. Both when-to-use and when-not-to-use are covered.

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