Skip to main content
Glama

Horseback: zajęcia na Jurze

Najbliższe wydarzenia

get_upcoming_events
Read-onlyIdempotent

Use this when the user asks what is on at Horseback or what to do on given dates: this weekend, holidays (ferie, Mikołajki, Sylwester), camps, picnics, riding competitions, events for children and teenagers. Returns dated events with time, admission, registration link and the content of the event page. Do not use for regular classes without a date (use get_activities).

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_upcoming_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
upcomingEventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "contact": {
      +      "description": "Horseback contact: phone, email, website, social profiles.",
      +      "type": "object"
      +    },
      +    "upcomingEvents": {
      +      "items": {
      +        "properties": {
      +          "buyNowUrl": {
      +            "description": "Online payment link (\"Kup teraz\" / Buy now) of an event with one variant sold online; payment on site is possible too.",
      +            "type": "string"
      +          },
      +          "buyNowUrls": {
      +            "description": "Online payment links per variant, for an event with several variants sold online.",
      +            "items": {
      +              "properties": {
      +                "buyNowUrl": {
      +                  "type": "string"
      +                },
      +                "variant": {
      +                  "type": "string"
      +                }
      +              },
      +              "required": [
      +                "variant",
      +                "buyNowUrl"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "date": {
      +            "description": "Start date (YYYY-MM-DD).",
      +            "type": "string"
      +          },
      +          "dateEnd": {
      +            "description": "End date of a multi-day event (YYYY-MM-DD), if any.",
      +            "type": "string"
      +          },
      +          "location": {
      +            "type": "string"
      +          },
      +          "moreInfo": {
      +            "description": "Link to the event page.",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "date"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "upcomingEvents"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful context beyond them: what the result contains (time, admission, registration link, event page content). It does not mention pagination, result caps, or that language selection affects all returned texts, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the usage trigger before the scope enumeration and the exclusion. Every element in the parenthetical list tightens the boundary of what counts as an event; nothing is redundant with the title or schema.

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?

With an output schema present and annotations covering the safety profile, the description needs only to establish purpose, scope and routing, all of which it does. The single optional parameter is fully handled by the schema, so no critical information for a correct call 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 the single language parameter is fully documented in the schema, including its default and enum values. The description says nothing about the language parameter or how it should be chosen, so it adds no meaning beyond the schema — the baseline of 3 applies.

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 (returns dated events) and resource (upcoming events at Horseback), and enumerates the concrete event types covered: camps, picnics, riding competitions, holidays. It explicitly distinguishes itself from get_activities, so an agent can route correctly 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?

Gives an explicit when-to-use trigger (user asks what is on at Horseback or what to do on given dates) with concrete date examples, plus an explicit when-not-to-use clause that names the alternative tool (get_activities) for undated regular classes. Both sides of the routing decision 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