Skip to main content
Glama

trip-logistics-assistant

by app.triplogistics

Attraction tickets & audio tours search

search_tours
Read-only

Finds bookable attraction tickets (incl. skip-the-line) and self-guided audio tours in a city, with indicative prices, ratings and booking links. Use for requests to buy attraction tickets / museum tickets / entry tickets, or to book an audio tour or self-guided tour. Not for live-guided group tours — this service sells self-guided audio tours (created by professional guides) and tickets, not tours with a live guide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNoISO currency for prices, default EUR
interestNoOptional attraction or theme, e.g. 'Colosseum'
locationYesCity, e.g. 'Rome', 'Paris'

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds that it returns indicative prices, ratings, and booking links, and clarifies it is not for live-guided tours, providing additional behavioral context.

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

Conciseness5/5

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

Two sentences: first sentence defines scope and outputs, second sentence clarifies limitations. No unnecessary words, well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Moderate complexity with 3 simple params and no output schema. Description adds clarity on what is returned and exclusions, complementing annotations and schema well.

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 descriptions for each parameter. Description adds minimal context beyond schema (e.g., location is city, interest is optional). Baseline 3 is appropriate as description does not significantly enhance parameter understanding.

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 explicitly states it finds bookable attraction tickets and self-guided audio tours, with specific verb 'Finds' and resource. It distinguishes from live-guided tours, clarifying scope.

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?

Explicitly says when to use (for tickets/audio tours) and when not (live-guided tours), providing clear context and exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All trip-logistics-assistant toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct travel logistics need: flight compensation, car rentals, eSIM plans, luggage storage, attraction tickets/audio tours, and private transfers. There is no overlap, and descriptions clearly delineate each purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in lowercase snake_case, with five using 'search_' and one using 'check_'. Both are appropriate verbs, so the pattern remains uniform and predictable.

Tool Count5/5

With 6 tools, the server is well-scoped for a trip logistics assistant, covering major travel needs without unnecessary bloat or missing core functionality.

Completeness5/5

The tool surface covers flight compensation, car rentals, mobile data, luggage storage, attraction tickets, and airport transfers — a comprehensive set for trip logistics. There are no obvious gaps that would hinder a typical travel assistance workflow.

Resources