Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

City guide

get_city_guide
Read-onlyIdempotent

Reads Adonde's own guide to one city. Returns the tagline, highlights, where to stay (neighbourhoods), a few tours picked for it, the best time to go and the app link. If we have no guide it says so; then offer start_trip and never describe the city as our guide. Reads only. Use when the traveller asks what to do or see in a city, or about one stop of a route; use get_place_details for one place on a trip, suggest_route to choose several cities, search_tours for the full tour list.

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": {
      "city": "<city>"
    },
    "name": "get_city_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity or town, e.g. Lisbon.
countryNoCountry name or ISO code, e.g. Portugal. Send it when known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description's 'Reads only' is mostly redundant. However, it adds useful behavioral context: what fields are returned and how to handle the absence of a guide without misrepresenting it as Adonde's own guide.

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 front-loaded with purpose and return contents, then moves to fallback behavior and routing guidance. It is dense but every sentence contributes useful selection or invocation information.

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?

Although there is no output schema, the description enumerates the key return fields and explains the no-guide case. Combined with the rich annotations and complete input schema, it gives an agent enough information to call the tool correctly.

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 100%, with both city and country clearly documented. The description reinforces that this is for one city but does not add syntax or selection guidance beyond the schema, so it meets the baseline rather than exceeding it.

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 verb and resource: reads Adonde's own guide to one city. It also enumerates the returned content and explicitly distinguishes the tool from siblings like get_place_details, suggest_route, and search_tours.

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 clear when-to-use guidance for city-level discovery and route-stop questions, and explicitly names alternative tools for nearby but different tasks. The no-guide fallback also tells the agent what to do when the tool cannot satisfy the request.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Adónde toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources