Skip to main content
Glama

Tickets: tours and event tickets in South America

Listar destinos

listar_destinos
Read-only

Lista os destinos cobertos, quantos passeios ou eventos cada um tem e a data da última conferência de preços.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the shape of the returned record (destination, count of tours/events, last price-check date), which matters since no output schema exists. It does not cover sorting, pagination, or whether the price-check date can be null for uncovered destinations.

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

Conciseness4/5

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

A single sentence with no filler, and the resource is front-loaded ahead of the return-field detail. It is efficient, though the enumeration of returned fields makes it slightly dense; a short clause on ordering or scope would cost it nothing.

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 zero-parameter, annotation-covered read tool with no output schema, the description supplies the one thing structured data lacks: what each listed item contains. Only minor gaps remain around result ordering and whether the price-check date is ever absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the listing is unfiltered and returns all covered destinations.

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 names a specific verb and resource ("Lista os destinos cobertos") and goes further to specify the content of each entry: tour/event counts and last price-check date. That distinguishes it clearly from buscar_passeios (search) and detalhes_passeio (single-item detail) by resource granularity, though it never explicitly names those siblings.

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: as a zero-parameter catalog lister, it reads as the natural entry point for discovering which destinations exist. There is no explicit statement of when to prefer it over buscar_passeios, nor any exclusion or precondition (e.g., call this first to obtain destination identifiers).

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