Skip to main content
Glama

Horseback: zajęcia na Jurze

Pomysły na prezent

get_gift_ideas
Read-onlyIdempotent

Use this when the user looks for a gift: a Christmas gift (prezent na święta, prezent świąteczny), a gift for a child, for an adult, for a family or for company employees (prezent dla pracowników), a gift voucher (bon upominkowy) or a riding pass (karnet) as a gift. Returns all items perfect as a gift from https://horseback.pl/idealne-na-prezent (the same list as the page): id, name, price, a link to the activity page, an online payment link ("Kup teraz" / Buy now) for items sold online, who the item is for (audience and the text of the activity page), and the purchase deadline sentence (purchaseDeadline) - tell it to the user. recipient only puts the items for that recipient first and budget_pln is only echoed back - nothing is left out; choose the items by forWhom, description and price, and check the activity page (get_activity_details) for age limits. Do not use for group trips or company team-building days (use get_group_trip_offer) or to take payment. 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

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the returned texts: "pl" (Polish, default) or "en" (English). Use the language of the conversation.
recipientNoOptional: who the gift is for - child, adult, family, or employees (company employees).
budget_plnNoOptional: maximum price of one item in PLN (echoed back; compare it with the prices yourself).

Output Schema

NameRequiredDescriptionDefault
noteNo
itemsYes
pageUrlYesThe gift page (all items perfect as a gift).
requestNorecipient and budget_pln from the call, echoed back (null where not given); they do not remove items.
languageYesLanguage of the returned texts.
payOnSiteNo
promotionNoCurrent voucher promotion sentence from the gift page - tell it to the user.
purchaseDeadlineYesSentence from the gift page on how vouchers are sent (field name kept) - tell it to the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / promotion
      Added value: +{
      +  "description": "Current voucher promotion sentence from the gift page - tell it to the user.",
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • changedInput schema / properties / budget_pln / description
      Previous value: -"Optional: maximum price of one item in PLN."New value: +"Optional: maximum price of one item in PLN (echoed back; compare it with the prices yourself)."
    • addedOutput schema / properties / items / items / properties / activityId
      Added value: +{
      +  "description": "Id of the activity page for get_activity_details (programme, FAQ with age limits and other conditions).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / items / items / properties / description
      Added value: +{
      +  "description": "Short description from the activity page (when the page has no \"for whom\" text).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / items / items / properties / forWhom
      Added value: +{
      +  "description": "\"For whom\" text from the activity page.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / items / items / properties / groupSize
      Added value: +{
      +  "description": "\"Group size\" text from the activity page (minimum group, how smaller groups are charged, when the price is quoted individually).",
      +  "type": "string"
      +}
    • changedOutput schema / properties / request / description
      Previous value: -"recipient and budget_pln from the call, echoed back (null where not given)."New value: +"recipient and budget_pln from the call, echoed back (null where not given); they do not remove items."
  3. Changed1 schema field changed
    • changedOutput schema / properties / purchaseDeadline / description
      Previous value: -"Purchase deadline sentence from the gift page - tell it to the user."New value: +"Sentence from the gift page on how vouchers are sent (field name kept) - tell it to the user."
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, so the bar is lower, yet the description still adds non-obvious behavior: recipient merely sorts items to the front and budget_pln is only echoed back rather than filtering ("nothing is left out"). It also instructs the agent to relay purchaseDeadline to the user and to present only returned programme/variants/prices, which guards against fabricated extras.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The trigger is correctly front-loaded, but the body is a single dense run-on mixing Polish parentheticals with English, and it re-enumerates return fields (id, name, price, link, payment link) that the output schema already defines. Each exclusion earns its place, but the field listing and term clutter add bulk without proportional value.

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?

For a read-only, zero-required-parameter listing tool with an output schema and full annotation coverage, nothing an agent needs is missing: trigger, scope, non-obvious parameter behavior, follow-up tool for age limits, and hallucination guardrails are all present. The output schema handles return-value documentation as allowed.

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 the baseline is 3, but the description adds meaning the schema lacks: recipient is an ordering hint, not a filter, and budget_pln is echoed rather than enforced, leaving price comparison to the caller. That is genuine semantics beyond the enum/description text, though language handling is not elaborated.

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 a concrete verb+resource (return gift-suitable items from horseback.pl/idealne-na-prezent) and enumerates the gift categories it covers (Christmas, child, adult, family, employees, voucher, karnet). It explicitly distinguishes itself from get_group_trip_offer and states it is not for taking payment, so an agent can separate it from every listed sibling.

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?

"Use this when the user looks for a gift" gives an explicit trigger, and the negative clause names the excluded cases (group trips, team-building days) plus the correct alternative (get_group_trip_offer). It also routes follow-up work: use get_activity_details to check age limits, and do not use this tool to take payment.

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