Skip to main content
Glama

LocalSpot Trip

find_places

Restaurants, cafés or bars in a Korean city, best first by local card payments. Optional: neighbourhood, food keyword, open at a given day and time. Up to 8 results.

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

Input Schema

NameRequiredDescriptionDefault
dayNoWeekday the traveller goes (optional)
areaNoNeighbourhood id or name from list_cities (optional)
cityYesCity id from list_cities, e.g. Seoul, Busan, Jeju
foodNoFood keyword in English or Korean, e.g. "bbq", "noodles", "국밥" (optional)
timeNoHH:MM 24h, must be open then (optional)
typeNoDefault meal
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/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 disclose two non-obvious traits: results are ordered 'best first by local card payments' and capped at 8. It omits what a result record contains and how failures (unknown city, unknown area) behave, but the ranking and cap are the key behavioral facts.

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?

Three short sentences, front-loaded with the resource and ranking, then optional filters, then the result cap. Nothing is padded, though the optional-filters sentence largely mirrors parameters the schema already labels as optional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should say more about what a returned place looks like (name, address, payment data, hours). It covers scope, ordering and result count adequately for a 7-parameter search tool but leaves the return shape undocumented.

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 86%, so the schema already explains city, area, food, day, time and limit with examples and enums. The description only restates which filters are optional and echoes the 8-result cap, adding no syntax or format detail beyond the schema.

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 resources (restaurants, cafés, bars), the geography (a Korean city) and the ranking principle (local card payments), so an agent knows exactly what it gets back. It does not name a sibling to contrast with, so the boundary against open_nearby or sights is only implied by the resource list.

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 implied by the phrasing 'in a Korean city' with optional filters, which suggests a city-scoped discovery search. There is no explicit when-to-use vs when-not guidance, and no mention of alternatives such as open_nearby for proximity-based lookups.

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