Skip to main content
Glama

Search places

search_places
Read-onlyIdempotent

Search Boken Japan listings (sights, things to do, places to eat, places to stay, day-to-day) by name or keyword, optionally within a prefecture and/or town and by category. Returns facts with the bokenjapan.com page, source URL, town access, checked booking links (stays) and last_verified.

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": {
      "query": "<query>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoTown slug or name, e.g. "hakuba" (best with prefecture)
limitNo
queryYesName or keyword, English or Japanese (e.g. "soba", "onsen", "Hakuba", "白馬")
categoryNosight | activity | food | stay | day_to_day, or a food category such as "cafe", "noodles", "seafood"
prefectureNoPrefecture slug or name, e.g. "nagano"

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?

The readOnly/idempotent/non-destructive annotations already cover the safety profile, so the description's real contribution is the return-shape disclosure (page URL, source URL, town access, checked booking links, last_verified), which tells the agent what freshness and provenance signals come back. Pagination behavior is left implicit in the limit parameter.

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 search surface and its filters, the second defines the payload. Both are front-loaded and every clause carries information.

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 no output schema, the description steps in to summarize returned fields, and the filter model is fully spelled out. For a 5-parameter read-only search this is nearly complete; only pagination and result-count behavior are unmentioned.

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 80% and the schema itself documents query, town, prefecture and category with examples, so the baseline of 3 applies. The description restates the filtering semantics ('by name or keyword, optionally within a prefecture and/or town and by category') but adds 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 a specific verb and resource (search Boken Japan listings) and enumerates the covered categories (sights, things to do, food, stay, day-to-day), so an agent knows exactly what corpus is queried. It stops short of contrasting itself with siblings like get_listing or list_towns, leaving that differentiation to inference.

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?

It signals that prefecture, town and category are optional refinements on a keyword search, which is useful context. It never states when to prefer this over get_listing for a known place or list_towns for browsing, and offers no explicit exclusions.

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