Skip to main content
Glama

不動産情報サービス MCP

by io.github.n-3inc

都道府県内の市区町村一覧取得 / City List in Prefecture

reinfolib-city-list
Read-only

国土交通省の不動産情報ライブラリから都道府県内の市区町村一覧を取得します。都道府県コードを指定して検索します。ここで得た市区町村コード（id）は reinfolib-real-estate-price の city 引数に渡せます。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYes都道府県コード: 北海道=01, 青森県=02, 岩手県=03, 宮城県=04, 秋田県=05, 山形県=06, 福島県=07, 茨城県=08, 栃木県=09, 群馬県=10, 埼玉県=11, 千葉県=12, 東京都=13, 神奈川県=14, 新潟県=15, 富山県=16, 石川県=17, 福井県=18, 山梨県=19, 長野県=20, 岐阜県=21, 静岡県=22, 愛知県=23, 三重県=24, 滋賀県=25, 京都府=26, 大阪府=27, 兵庫県=28, 奈良県=29, 和歌山県=30, 鳥取県=31, 島根県=32, 岡山県=33, 広島県=34, 山口県=35, 徳島県=36, 香川県=37, 愛媛県=38, 高知県=39, 福岡県=40, 佐賀県=41, 長崎県=42, 熊本県=43, 大分県=44, 宮崎県=45, 鹿児島県=46, 沖縄県=47
languageNo出力結果の言語 (ja:日本語, en:英語)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes市区町村一覧

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description discloses the data source (国土交通省の不動産情報ライブラリ) and the purpose of the returned IDs, which complements the readOnlyHint and destructiveHint annotations. It doesn't contradict annotations and adds cross-tool integration context.

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?

The description consists of two succinct sentences that front-load the core function and then explain the downstream use. No redundant information.

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

Completeness5/5

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

With output schema present and annotations covering safety, the description conveys the tool's purpose, usage, and downstream integration. The mention of passing codes to reinfolib-real-estate-price completes the context.

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 the prefecture code mapping and language option are already documented. The description only echoes '都道府県コードを指定して検索します' which adds no new parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description specifies a clear verb ('取得する' - retrieve) and resource ('不動産情報ライブラリ' - real estate info library) with scope ('都道府県内' - within a prefecture). It also distinguishes from the sibling reinfolib-real-estate-price by explaining the city codes are used as input for that tool.

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?

The description provides context by stating the result can be passed to reinfolib-real-estate-price's city argument, which implies when this tool is useful. It doesn't explicitly mention exclusions or alternatives, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 不動産情報サービス MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get-time retrieves current time, reinfolib-city-list gets city codes, and reinfolib-real-estate-price gets price data. No overlap in functionality.

Naming Consistency2/5

Naming is inconsistent: 'get-time' uses a kebab-case verb-noun pattern, while 'reinfolib-city-list' and 'reinfolib-real-estate-price' use snake_case with a 'reinfolib-' prefix and different term order. No uniform convention.

Tool Count2/5

Only 3 tools, which is too few for a real estate information service. The inclusion of 'get-time' seems unrelated and suggests the server may have a mixed or ambiguous scope.

Completeness2/5

Missing essential tools like prefecture list, station list, property details, or search by multiple criteria. The set covers only city lookup and price, leaving significant gaps for real estate information retrieval.

Resources