Skip to main content
Glama

Send feedback to SlickTrip

share_feedback

Use only when the traveler has told you, in this conversation, how SlickTrip is doing for them (a number from 1 to 5) or what they like or would change, and is happy for it to go to SlickTrip's team. Send their number as rating and their own words as they said them; never invent, soften or add to their opinion, and never send anything else from the conversation. SlickTrip keeps them with their account to improve the service. Needs a signed-in account.

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": "share_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
likesNoWhat the traveler likes about SlickTrip, in their own words.
ratingNoHow SlickTrip is doing for them, 1 (not great) to 5 (love it), only when they gave a number.
commentNoAnything else they want the team to know, in their own words.
would_changeNoWhat the traveler would change or add, in their own words.

Output Schema

NameRequiredDescriptionDefault
codeNoOn an error: a machine-readable kind, e.g. unknown_place
noteNoWhat to tell the traveler next
fieldNoOn unknown_place: which argument (origin, destination, ...)
statusNook | error | sign_in_required
messageNoThat the words reached SlickTrip's team, or the error
suggestionsNoOn unknown_place: places to offer the traveler, each with code, name, kind (airport, all airports in the city, nearby airport), city, country
places_assumedNoPlace names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-open-world write with no destructive effect, so the safety bar is pre-set. The description adds genuinely useful context beyond them: the account is required ('Needs a signed-in account') and the data is retained against the traveler's account to improve the service. It does not mention whether repeated sends create duplicate submissions, which is the main residual gap for a non-idempotent write.

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?

It is a single dense block, and every clause carries an operational constraint rather than filler. The main cost is that it opens with the usage condition instead of the action, slightly burying the purpose, and the run-on sentence makes it harder to scan than a short bulleted structure would.

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 covers the response, and annotations cover the safety profile, so the description only needs to cover preconditions, sourcing fidelity, privacy/retention and auth - all of which are present. Nothing an agent needs in order to call this correctly is missing.

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 field-level meaning is already documented, giving a baseline of 3. The description still adds sourcing semantics the schema cannot express: the rating must be the traveler's stated number and the remaining fields must be their words 'as they said them', never invented, softened or padded from elsewhere in the conversation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: sending the traveler's own rating (1-5) and words to SlickTrip's team. The scope is narrow enough that confusion with travel-search siblings is essentially impossible, although no sibling is named as an alternative or contrast.

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 preconditions ('only when the traveler has told you, in this conversation... and is happy for it to go to SlickTrip's team') and explicit exclusions ('never send anything else from the conversation'). The agent knows both the trigger and the boundary without 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.