Skip to main content
Glama

Horseback: zajęcia na Jurze

Cennik

get_price_list
Read-onlyIdempotent

Use this when the user asks about price or cost at Horseback (ile kosztuje jazda konna, cena hipoterapii, karnet, obóz, wycieczka, strzelnica). Returns the current price list (same as https://horseback.pl/cennik): item id, activity name, price text, a link to the activity page, who it is for (audience: individual, family, kindergarten, school, wtz (occupational therapy workshop (WTZ)), company, public_office) and occasions (birthday, bachelor_party (bachelor/bachelorette party), wedding, first_communion, corporate_event (company event/team-building), school_trip, gift). To show a group the items that fit the conversation, pick them by audience and occasions and pass their ids in item_ids of get_group_trip_offer. Prices are kept as text ("od" / "from", per person, per group); "wycena indywidualna" / individual quote means the price is quoted after the inquiry - do not invent a number. Do not use to take payment - no payment is taken through these tools.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the returned texts: "pl" (Polish, default) or "en" (English). Use the language of the conversation.

Output Schema

NameRequiredDescriptionDefault
noteNo
itemsYes
languageYesLanguage of the returned texts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / items / items / properties / audience
      Added value: +{
      +  "description": "Who the item is for (audience): code and label in the language of the response.",
      +  "items": {
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / items / items / properties / id
      Added value: +{
      +  "description": "Stable id of the price-list item (pass it in item_ids of get_group_trip_offer).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / items / items / properties / occasions
      Added value: +{
      +  "description": "Occasions the item fits (may be empty): code and label in the language of the response.",
      +  "items": {
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "code",
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
      -  "name",
      -  "price"
      -]New value: +[
      +  "id",
      +  "name",
      +  "price",
      +  "audience",
      +  "occasions"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "items": {
      +      "items": {
      +        "properties": {
      +          "buyNowUrl": {
      +            "description": "Online payment link (\"Kup teraz\" / Buy now), only for items sold online; payment on site is possible too.",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "price": {
      +            "description": "Price as text, e.g. \"od 100 zł / os.\" or \"wycena indywidualna\".",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Activity page, or null.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "price"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "language": {
      +      "description": "Language of the returned texts.",
      +      "enum": [
      +        "pl",
      +        "en"
      +      ],
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "language",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real behavior: prices are kept as text ('od'/'from', per person, per group) and 'wycena indywidualna' means a quote follows the inquiry, so the agent must not invent a number. It also clarifies no payment flows through these tools, which is beyond what the annotations say. It does not discuss caching or staleness of the price list, a small remaining gap.

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 trigger condition, then return fields, then the chaining instruction, then the pricing caveat. It is dense but nearly every clause carries actionable meaning; the long parenthetical glosses of audience and occasion values are somewhat verbose, though they aid interpretation of the returned data.

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?

An output schema exists so return values need not be re-explained, annotations carry the safety profile, and the schema fully documents the only parameter. The description still supplies the domain semantics (audience, occasions, text prices, individual quotes) an agent needs to answer a pricing question correctly without fabricating figures.

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?

There is a single optional parameter whose schema description is at 100% coverage and already explains the pl/en enum and default. The description never mentions the language parameter, so it adds nothing beyond the schema here; baseline 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 and resource ('Returns the current price list') and enumerates exactly what comes back: item id, activity name, price text, link, audience, occasions. It also lists the user phrasings that trigger it (cena hipoterapii, karnet, obóz), so it is unmistakable against siblings like get_activities or get_gift_ideas.

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 (price or cost questions), names the concrete next step ('pass their ids in item_ids of get_group_trip_offer') for group offers, and states an exclusion ('Do not use to take payment - no payment is taken through these tools'). That is when/when-not/where-next in three sentences.

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