Skip to main content
Glama
sugukurukabe

japan-real-estate-intel

cross_analyze_real_estate_market

Read-only

Analyze real estate market across 10 prefectures, combining land prices, investment scores, foot traffic, education, and corporate data for comprehensive insights.

Instructions

Cross-analyze real estate market: land price trends, investment score, foot traffic, education, corporate presence. 10 prefectures. | 不動産市場クロス分析。地価・投資スコア・人流・教育・企業立地を総合分析。10都道府県対応。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYesエリア(例: '名古屋市中村区', '世田谷区')
timeRangeYes
prefectureNo都道府県名(和名/英名/ISO 3166-2 コード対応)愛知県
includeRiskNo災害リスクを考慮するか
output_modeNoOutput verbosity. compact=TL;DR + key numbers only (default), detailed=full Markdown report | 出力詳細度。compact=主要数値のみ(デフォルト)、detailed=全文レポート付きcompact
focusMetricsNo
neighborhoodNo町丁目(例: '名駅南1丁目')。v2.4 では町丁目レベル実データに対応(対応都道府県のみ)
propertyTypeYes
includeMedicalNo医療・福祉施設データを含むか(対応都道府県のみ)
includeCorporateNo企業立地データを含むか(対応都道府県のみ)
includeEducationNo教育環境データを含むか(対応都道府県のみ)
includeHumanFlowNo人流データを含むか(対応都道府県のみ)
includeTransportNo交通利便性データを含むか(対応都道府県のみ)
includeCommercialNo商業施設データを含むか(対応都道府県のみ)
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety profile is clear. Description adds no significant behavioral context beyond that, but does not contradict annotations.

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?

Description is two sentences in English and Japanese, front-loaded with key purpose and scope. Every part earns its place with no fluff.

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 complex tool with 14 parameters, the description effectively summarizes the main analysis dimensions and scope. It does not need to explain return values as no output schema exists, and the description suffices for selection.

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?

Schema coverage is 79%, and description adds value by noting the tool supports '10 prefectures' and specifying version capabilities for neighborhood-level data. This goes beyond the schema, providing useful context.

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 clearly states the tool performs cross-analysis of real estate market, listing specific dimensions (land price, investment score, foot traffic, education, corporate presence) and scope (10 prefectures). This distinguishes it from sibling tools that focus on single aspects.

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?

Description implies use for comprehensive cross-analysis, but does not explicitly state when to use this tool vs. alternatives or provide exclusion criteria. Context is clear but lacks direct guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sugukurukabe/japan-real-estate-intel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server