Skip to main content
Glama

list_activity_cities

Diz se uma cidade tem PASSEIOS (cobertura) e devolve o slug dela, que e o zona de list_activities. q: texto da cidade (ex.: 'cancun', 'mexico city'); ao menos 2 letras; volta no maximo 20, as de mais hoteis primeiro. Sem resultado NAO prova que a cidade nao tem passeios (a lista pode estar incompleta): tente list_activities com o slug da cidade e so conclua que nao ha passeios se ele responder 'sem passeios'; nunca use cidade vizinha. rotulo e o nome no idioma do hospede; venda diz se o site esta vendendo passeio e venda_traslado se vende traslado (search_transfers; ligado so quando for true). Passeios sao cobrados SO em USD (Stripe). language: 'en', 'pt' ou 'es'. token: aceito por compatibilidade e ignorado aqui (a lista e publica).

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": {
      "q": "<q>"
    },
    "name": "list_activity_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
tokenNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: the endpoint is public (token accepted but ignored), returns at most 20 results ordered by hotel count, bills tours only in USD via Stripe, and can be incomplete. It also explains the meaning of the output fields `rotulo`, `venda`, and `venda_traslado`, none of which appear in structured data.

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?

Purpose and the critical fallback rule are front-loaded, and little is wasted, but the paragraph is a run-on that interleaves output-field meanings, currency notes, and parameter constraints, which makes it denser than it needs to be. Splitting output semantics from parameter constraints would improve scanability.

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?

There is no output schema and no annotations, yet the description covers result cardinality and ordering, the incompleteness caveat with a concrete recovery path, the response fields, and the currency/payment constraint. Nothing an agent needs to call it correctly or interpret its response is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it documents all three parameters: `q` is city text with a two-letter minimum and examples, `language` accepts 'en', 'pt', or 'es', and `token` is accepted for compatibility but ignored because the list is public.

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 states a specific purpose: tell whether a city has tours (coverage) and return its `slug`, which it explicitly maps to the `zona` parameter of list_activities. That mapping alone lets an agent distinguish it from list_activities and search_transfers without opening either schema.

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?

It gives explicit when-to-use and when-not-to guidance: an empty result does not prove the city lacks tours, so the agent should fall back to list_activities with the city slug and only conclude 'no tours' if that tool answers 'sem passeios'; it also forbids substituting a neighboring city. It additionally routes transfers to search_transfers, conditioned on venda_traslado being true.

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