Skip to main content
Glama

Tuki — Travel Marketplace (Chile y Latinoamérica)

by cl.tuki

Búsqueda unificada (todas las verticales)

search_unified
Read-onlyIdempotent

Single concise search across ALL Tuki verticals at once — experiences, accommodations, hotels, reservation centrals, events (ticketing) and car rental. Use when the user query is open or could match more than one vertical. Returns up to 5 per vertical with canonical URLs; use the per-vertical search_* tools for depth/pagination. Routing rule: use THIS tool when one location/query spans verticals; use search_* for a concrete product; use recommend for planning / open-ended intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch text.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds concrete behavioral details: returns up to 5 per vertical, includes canonical URLs, and lacks depth/pagination (which per-vertical tools provide). This goes beyond the annotation baseline.

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?

Four sentences, each earning its place: purpose, usage trigger, output behavior, and routing rule. Front-loaded with the core purpose, no filler.

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?

For a multi-vertical search with no output schema, the description covers what results look like (up to 5, canonical URLs), and how to get more depth. Minor gap: no mention of result ordering or error handling, but not essential for selection/invocation.

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?

Input schema has one parameter with 100% coverage (query described as 'Search text.'). The description does not add extra syntax details, but none are needed for such a simple parameter. Baseline 3 is appropriate.

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 opens with a specific verb ('Single concise search') and resource ('ALL Tuki verticals'), then enumerates them. It clearly distinguishes itself from sibling per-vertical search tools by emphasizing cross-vertical capability.

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 states when to use this tool ('user query is open or could match more than one vertical') and provides a routing rule contrasting it with search_* and recommend. This is textbook usage guidance with named alternatives.

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

All Tuki — Travel Marketplace (Chile y Latinoamérica) 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.4/5.0
Disambiguation5/5

Every tool targets a distinct resource or action: get_* tools retrieve details for specific entity types, search_* tools query specific verticals, and list_* tools enumerate categories. The potential overlap between search_accommodations and search_hotels is explicitly disambiguated in descriptions, and search_unified vs per-vertical searches have clear routing rules.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_*_detail for lookups, search_* for queries, list_* for enumerations, and recommend as the sole one-word but still predictable exception. Naming is uniform with snake_case throughout, making the overall structure highly predictable.

Tool Count4/5

With 23 tools, the server is on the heavier side, but the breadth of verticals (accommodations, cars, events, experiences, hotels, destinations, bus routes, travel guides, solutions) justifies each tool's presence. The number is slightly above the ideal but still well-scoped for a multi-category marketplace.

Completeness5/5

The tool surface covers the full browsing and recommendation lifecycle: search and list across verticals, retrieve detailed information for any entity, access editorial travel guides, and generate checkout URLs for booking. No critical operations are missing for the server's purpose as a read-only recommendation and conversion layer.

Resources