Skip to main content
Glama

Tickets: tours and event tickets in South America

Buscar passeios e ingressos

buscar_passeios
Read-only

Busca passeios, ingressos e experiências por destino e texto livre (pt, es ou en). Devolve nome, preço de referência, vendedor e o link 'comprar' do parceiro.

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

Input Schema

NameRequiredDescriptionDefault
textoNoO que a pessoa procura, ex.: navegação canal Beagle, minitrekking, Snowland, setor A Interlagos
limiteNoQuantos resultados (1 a 30, padrão 10)
destinoNoDestino ou evento, ex.: Bariloche, Gramado, Ushuaia, Cartagena, El Calafate, Interlagos, F1
preco_maxNoPreço máximo na moeda do destino (BRL, ARS ou COP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by naming the returned fields (nome, preço de referência, vendedor, link 'comprar' do parceiro), which matters because there is no output schema. It omits pagination/empty-result behavior and any note on currency or price accuracy.

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, zero filler: the first establishes what is searched and how, the second lists what comes back. Front-loaded and appropriately sized for a search tool.

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?

With all parameters optional, full schema coverage, and no output schema, the description fills the main gap by enumerating the return fields and confirming multilingual input. It is nearly complete; only result-count behavior and the meaning of 'preço de referência' versus actual purchase price are left unstated.

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%, so all four parameters (texto, limite, destino, preco_max) are already documented with examples and ranges. The description only echoes the destino/texto axes and the multilingual aspect, adding no syntax or edge-case guidance (e.g., combining destino with texto, or how preco_max interacts with the destination currency). Baseline 3 applies.

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?

States a specific verb ('Busca') and concrete resources ('passeios, ingressos e experiências'), plus the search axes (destino and free text) and language coverage. It does not name the sibling tools (detalhes_passeio, listar_destinos) to draw a boundary, so it falls short of a 5, but the purpose 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the discovery/search entry point, and 'por destino e texto livre' hints at how to query. There is no explicit when-to-use versus detalhes_passeio or listar_destinos, and no statement of when this tool is the wrong choice.

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