Skip to main content
Glama

Horseback: zajęcia na Jurze

Szkolenie z reagowania w sytuacjach zagrożenia i samoobrony

get_safety_training_offer
Read-onlyIdempotent

Use this when the user asks how to prepare people for a dangerous situation or looks for self-defence training for a group: how to prepare employees, pupils, a school or a company for a threat (jak przygotować pracowników, uczniów, szkołę lub firmę na sytuację zagrożenia), how to behave during a knife attack or a terrorist attack (atak nożownika, atak terrorystyczny), conflict de-escalation (deeskalacja konfliktu), peer violence (przemoc rówieśnicza), self-defence for women (samoobrona dla kobiet), self-defence or threat-response training for children, teenagers, adults, seniors or families (szkolenie z samoobrony, zajęcia z samoobrony, szkolenie z reagowania na zagrożenie). Returns the page of the Horseback group classes in threat response with self-defence basics: for whom, topics, programme, duration, price and how it is charged, group size, place, transport for groups, FAQ, the page link and how to sign up (pre-reservation form or create_prereservation, phone, SMS). The tool does not check free dates. Do not use for weapons training or for buying self-defense equipment. 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_safety_training_offer"
  }
}

Input Schema

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

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered; the description goes further by disclosing a real limitation ('The tool does not check free dates') and by constraining output ('Present only the programme, variants and prices returned by the tools; do not add elements'). That tells the agent both what the tool will not do and how to handle its result, which is behavior beyond the structured fields.

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 correctly with the usage trigger, then the return payload, then exclusions and output constraints — a sensible ordering. It is dense and long, with heavy bilingual keyword lists in parentheses, though those lists plausibly earn their place for matching Polish-language user queries.

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 one-parameter read tool with no output schema, the description is complete: it describes what the returned page contains, the sign-up routes, the absence of availability checking, and the framing constraint on presenting prices. Nothing an agent needs in order to call and use it 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?

The single parameter (language, pl/en enum) is documented at 100% schema coverage, so the baseline is 3. The description never mentions the language parameter or what it affects, so it adds no meaning beyond the enum's own description.

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 page of the Horseback group classes in threat response with self-defence basics') and enumerates exactly what that page contains (for whom, topics, programme, duration, price, group size, place, transport, FAQ, link, sign-up). It also draws negative boundaries that separate it from siblings: not weapons training, not equipment purchase, and sign-up belongs to create_prereservation.

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?

Opens with an explicit trigger ('Use this when the user asks how to prepare people for a dangerous situation...'), lists the concrete user phrasings and topics that should route here, and names the exclusions (weapons training, buying self-defence equipment) plus the alternative path for booking (pre-reservation form or create_prereservation). Nothing about when to select it is left to inference.

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