Skip to main content
Glama

Horseback: zajęcia na Jurze

Send feedback

send_feedback

Use this when you want to send general feedback to the owner of horseback.pl: about the data returned by the Horseback tools (missing information, an unclear price, an error), how the tools work, missing features, or anything else that would help agents and their users. Not for bookings, customer inquiries or personal data - to contact Horseback for the user, use the contact details from howToInquire (get_group_trip_offer). Do not include personal data (names, phone numbers, e-mail addresses, health information). Returns a short confirmation; there is no reply to the feedback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoOptional: the tool the feedback is about.
messageYesThe feedback: about the data, how the tools work, missing features or anything else, max 1000 characters. No personal data.
languageNoOptional: language of the message, "pl" or "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "get_activities",
      -  "get_activity_details",
      -  "get_price_list",
      -  "get_upcoming_events",
      -  "get_group_trip_offer",
      -  "get_directions",
      -  "get_safety_training_offer"
      -]New value: +[
      +  "get_activities",
      +  "get_activity_details",
      +  "get_price_list",
      +  "get_upcoming_events",
      +  "get_group_trip_offer",
      +  "get_directions",
      +  "get_safety_training_offer",
      +  "get_gift_ideas"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "get_activities",
      -  "get_activity_details",
      -  "get_price_list",
      -  "get_upcoming_events",
      -  "get_group_trip_offer",
      -  "get_directions"
      -]New value: +[
      +  "get_activities",
      +  "get_activity_details",
      +  "get_price_list",
      +  "get_upcoming_events",
      +  "get_group_trip_offer",
      +  "get_directions",
      +  "get_safety_training_offer"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "get_group_trip_offer",
      -  "get_upcoming_events",
      -  "get_price_list",
      -  "get_activities"
      -]New value: +[
      +  "get_activities",
      +  "get_activity_details",
      +  "get_price_list",
      +  "get_upcoming_events",
      +  "get_group_trip_offer",
      +  "get_directions"
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already convey the safety profile (non-readOnly, non-destructive), and the description adds real context beyond them: that it returns only a short confirmation, that there is no reply, and the prohibition on personal data. It does not cover rate limits or failure behavior, 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?

The usage condition and exclusions are front-loaded, and each sentence carries a distinct instruction (when to use, when not to, privacy rule, return behavior). The parenthetical examples of feedback types add slight verbosity but are useful for judgment.

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 three-parameter submission tool with no output schema, the description covers purpose, exclusions, alternative routing, privacy constraints, and expected return behavior. An agent has everything needed to decide and invoke correctly.

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 coverage is 100% with enums for tool and language already documented, so the schema does the heavy lifting. The description reinforces the message content and the no-personal-data constraint, but adds little syntactic or format detail beyond the schema.

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 states a specific verb and resource ('send general feedback to the owner of horseback.pl') and enumerates the feedback categories it covers (missing data, unclear price, errors, tool behavior, missing features). It clearly sets itself apart from sibling tools by naming howToInquire/get_group_trip_offer as the path for customer contact.

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?

It gives explicit when-to-use guidance, explicit exclusions ('Not for bookings, customer inquiries or personal data'), and names the alternative tool to use instead for contacting Horseback on the user's behalf. There is no ambiguity left for the agent.

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