Skip to main content
Glama

Search tourist spots

search_spots
Read-onlyIdempotent

Search tourist spots in Japan by keyword, prefecture and category. 観光スポットを検索する。キーワード、都道府県、カテゴリで絞り込み可能。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_spots"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-100, default 20)
keywordNoKeyword matched against spot name/address (Japanese, e.g. "温泉", "城")
categoryNoSpot category key(s), comma separated. See list_spot_categories (e.g. nature_mountain, culture_shrine_temple)
prefectureNoPrefecture in English or Japanese (e.g. "Tokyo", "Kyoto", "東京都")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Spot category key(s), comma separated. See list_spot_categories (e.g. nature_mountain, culture_shrine_temple)"
    • addedInput schema / properties / keyword / description
      Added value: +"Keyword matched against spot name/address (Japanese, e.g. \"温泉\", \"城\")"
    • addedInput schema / properties / limit / description
      Added value: +"Max results (1-100, default 20)"
    • addedInput schema / properties / prefecture / description
      Added value: +"Prefecture in English or Japanese (e.g. \"Tokyo\", \"Kyoto\", \"東京都\")"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the Japan scope, which is genuine new context, but says nothing about result ordering, pagination behavior with limit, or behavior on no matches.

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?

Two short sentences, front-loaded with the verb and the filter axes. The second sentence is a full Japanese restatement of the first, which is defensible for a Japan-focused tool but is redundant for an agent that parses English.

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?

Annotations cover the safety profile, all four parameters are documented in the schema, and an output schema exists, so the description's remaining burden is small. However, for a search tool with four optional filters it omits any guidance on combining filters, default result behavior, or how it differs from the nearby-search siblings.

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%, so each of the four parameters (limit, keyword, category, prefecture) is already documented with examples and defaults; baseline is therefore 3. The description restates the same three filter field names without adding combining rules, multi-value semantics, or matching behavior beyond what the schema provides.

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?

States a specific verb and resource ("Search tourist spots") and names the three filter axes plus the geographic scope (Japan). It does not distinguish itself from the nearest sibling, search_nearby_spots, so an agent must infer that this is the non-geo keyword/filter search rather than being told.

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?

The filter list implicitly signals the intended use case (filtering by keyword/prefecture/category), which contrasts loosely with the proximity-based sibling, but there is no explicit when-to-use, when-not-to-use, or named alternative. All parameters are optional, and the description never says what happens when all are omitted.

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