Skip to main content
Glama

Tickets: tours and event tickets in South America

Detalhes de um passeio

detalhes_passeio
Read-only

Todos os dados de um passeio ou evento a partir do site e do id devolvidos por buscar_passeios (inclui todas as ofertas de um evento de automobilismo).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "id": "<id>"
    },
    "name": "detalhes_passeio"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 useful scope by saying it returns all tour/event data and all offers for a motorsport event, but it does not discuss error behavior, missing ids, or rate limits.

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 definition is a single front-loaded sentence with no filler. The parenthetical about motorsport offers adds concrete scope without bloating the description.

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 simple two-parameter detail-fetch tool with read-only annotations and no output schema, the description is largely complete: it states the input source and output scope. The only minor gap is that it does not elaborate on the site enum or invalid-id behavior.

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 0%, so the description should carry more parameter meaning. It adds that both site and id come from buscar_passeios, which is useful provenance, but it does not explain the site enum values or id format beyond that.

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 clearly states that it returns all data for a tour or event using site and id, and explicitly ties the id to buscar_passeios. It distinguishes this from the search tool by positioning itself as the detail retrieval step, though it does not use an explicit verb like 'retorna' or 'obtém'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives clear workflow context by saying the id comes from buscar_passeios, which tells the agent this should be used after searching. It does not provide explicit exclusions or compare against listar_destinos, but the prerequisite is clear.

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