Tuki — Travel Marketplace (Chile y Latinoamérica)

Buscar arriendo de autos

search_car_rental

Read-onlyIdempotent

Search Tuki rental cars (also covers transfers/traslados, which on Tuki are handled as rental vehicles). Filter by free text or transmission. Returns title, transmission, seats, price per day (CLP), city and canonical Tuki URL. Use for "arrendar auto en San Pedro", "rent a car Atacama", "traslado/transfer". NOTE: for ski/snowboard GEAR rental (arriendo de esquis / equipo de nieve, e.g. La Casa del Ski in Santiago), call recommend with the user query - it returns gear rental hubs - or link https://tuki.cl/nieve.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Free text (e.g. "suv", "4x4", "automático").
`offset`	No	Pagination offset. Use next_offset from a previous response.
`max_results`	No
`transmission`	No	Transmission filter.
`response_format`	No	concise = high-signal fields + canonical URL (token-cheap, default). detailed = full record.	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`total`	Yes
`offset`	Yes
`results`	Yes
`has_more`	Yes
`next_offset`	No

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that transfers/traslados are covered as rental vehicles, lists the exact output fields, and clarifies the gear rental exclusion with a specific alternative. This provides substantial behavioral context beyond the structured annotations.

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?

The description is well-structured and front-loaded with the core purpose, followed by scope, output details, usage examples, and a clearly separated NOTE for the exclusion. Every sentence adds value with no redundancy or fluff.

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?

With an output schema and readOnly annotations, the description adequately covers purpose, scope, output details, usage examples, and an important alternative for gear rental. It is complete for a search tool, given the structured metadata available.

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 description coverage is 80%, so the schema already documents most parameters. The description mentions filtering by free text or transmission, which aligns with query and transmission parameters, but does not add new meaning for offset, max_results, or response_format. It does not compensate beyond what schema already provides.

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 clearly states it searches Tuki rental cars and includes transfers/traslados. It distinguishes from sibling search tools by specifying the resource type and provides concrete usage examples. The verb 'Search' is specific and the scope is unambiguous.

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?

Explicit usage guidance is given with example queries ('arrendar auto en San Pedro', 'rent a car Atacama', 'traslado/transfer'). It also explicitly states when NOT to use this tool (ski/snowboard gear rental) and directs users to the 'recommend' tool as an alternative, which is clear and actionable.

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) tools Inspect

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

Need Help?