Skip to main content
Glama

エリア別の在庫

list_areas
Read-onlyIdempotent

都道府県別の施設数・主要エリアと、編集部のエリア特集ページ一覧を返します。検索前の当たり付けに使います。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent, closed-world read operation, so the safety profile is covered by structured data. Because no output schema exists, the description carries the real burden of describing the returned content, and it does so (counts by prefecture, major areas, feature-page list). It omits any sense of result size or whether IDs versus display names are returned.

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 short sentences, with the return content stated first and the usage note second. No filler, no restatement of the title alone, and it reads well after translation into a token-efficient call.

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?

For a zero-parameter read tool with no output schema, the definition covers what it returns and why to call it. The one gap is that it does not clarify whether the returned area names or IDs are the values needed to filter a subsequent search_hotels call, which is the main reason an agent would call this first.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the description needs no parameter detail; the baseline for zero-param tools applies. Nothing in the text conflicts with the empty 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 set: it returns facility counts by prefecture, major areas, and a list of editorial area feature pages. That is clearly distinct from the sibling tools get_hotel and search_hotels. It only falls short of a 5 because 'list_areas' suggests area identifiers, yet the description does not say whether the returned areas can be used as filter values in search_hotels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says to use this 'for initial reconnaissance before searching', which gives an explicit context for calling it. It does not name a specific alternative or say when not to use it, but the recommended position in the workflow is unambiguous.

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