Skip to main content
Glama

Maya's recommended places in a city

search_recommendations
Read-only

Places from Maya's city maps (attractions, hidden gems, local experiences, cafes, restaurants, nightlife, shopping) with a Google Maps link. Returns at most 10 places per call, plus the link to the full map.

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

Input Schema

NameRequiredDescriptionDefault
cityYesFor example "Hanoi", "Hoi An", "Bangkok", "Siem Reap", "Luang Prabang", "Seoul".
limitNo
queryNoOptional free text, for example "coffee", "rooftop", "market".
categoryNoOptional, for example "Cafes", "Restaurants", "Hidden gems", "Attractions".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of 10 places per call and the fact that a Google Maps link to the full map is returned, which tells the agent how to handle a user wanting more than ten results.

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?

Two sentences with no filler: the first defines the content and its source, the second defines the result size and return payload. The most decision-relevant information is front-loaded.

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?

With four simple parameters, one required, no nesting, and no output schema, the description covers the essentials, including return contents and the result cap that the missing output schema would otherwise have to convey. Minor gaps remain around what happens with an empty or unrecognized city and whether the query and category filters combine.

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 75% and the schema already documents city examples, free-text query, and category examples, so the baseline applies. The description only reinforces the 10-item ceiling implied by the limit parameter's maximum and lists categories that map onto the category parameter; it adds no syntax, matching, or fallback guidance.

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 the concrete resource ('Places from Maya's city maps') and enumerates the categories covered (attractions, hidden gems, cafes, restaurants, nightlife, shopping), so an agent knows exactly what kind of result to expect. It stops short of explicitly contrasting itself with any sibling, but the sibling set contains no comparable place-search tool, so confusion risk is low.

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: an agent can infer this is the tool for 'recommend me places in city X', and the required city parameter reinforces that. There is no statement of when not to use it, no prerequisites, and no pointer to an alternative for itinerary or trip-planning needs.

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