Skip to main content
Glama
Sign In

Adónde

by com.getadonde
OverviewDiscussionsAdmin

Place details

get_place_details
Read-onlyIdempotent

Reads one sight, restaurant or free item from a trip's menu or day plan, from the records the Adonde app shows. Returns photos, the description with its source, category or cuisine, area, address and map point, opening hours (flagged when unchecked), rating and reviews, price level, entry fee, phone, website, menu link and why it is listed. A field the records lack is absent; never fill one in. Reads only. Use for a menu id or a day item's cand; use get_tour_details for a bookable tour (an id like viator:CODE), get_city_guide for a whole city.

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": {
      "id": "<id>"
    },
    "name": "get_place_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe menu item's id (get_menu) or the day item's cand (get_trip), like osm:node/123 or viator-attraction:105.
cityNoThe item's city, sent with name.
nameNoThe item's name, used when the id is not on record.
trip_idNoThe trip's id (trip_id), as returned by start_trip or list_trips. The trip the item is on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds the valuable anti-hallucination rule 'A field the records lack is absent; never fill one in' and enumerates what is returned (opening hours flagged when unchecked, etc.). It does not cover failure behavior when the id is unknown or what happens if only name/city are supplied.

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?

Front-loaded with the action and routing, with no filler sentences. The long enumeration of returned fields is dense but earns its place given there is no output schema.

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?

With no output schema, the description carries return-value disclosure and does so thoroughly, plus routing to siblings and the absent-field rule. Nothing essential for a correct call is missing.

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 the meaning of id, city, name and trip_id is already documented in the schema, including the id/cand examples. The description adds only the usage framing for id, so the baseline 3 applies.

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?

States a specific verb and resource ('Reads one sight, restaurant or free item from a trip's menu or day plan') and explicitly separates itself from get_tour_details and get_city_guide. An agent can pick this tool without opening the 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?

Gives explicit routing: use for a menu id or a day item's cand, use get_tour_details for a bookable tour id like viator:CODE, use get_city_guide for a whole city. When-to-use and when-not-to-use are both stated with named alternatives.

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