Skip to main content
Glama
sugukurukabe

japan-real-estate-intel

ChatGPTビジュアル要約

quick_visual_summary
Read-only

Renders a real estate visual summary with maps, charts, and recommended next actions for investment analysis or area comparison.

Instructions

Render a ChatGPT-optimized real estate visual summary with map, charts, recommended next actions, and compact markdown fallback. Always use this when the user asks to show, visualize, compare, or continue in ChatGPT. | ChatGPT向けに地図・グラフ・次アクション・要約をまとめて表示するレンダーツール。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNoTarget area to focus the visual summary on | 表示対象エリア
modeNoDashboard mode | ダッシュボード表示モード2d
intentNoUser goal for choosing the best visual starting point | 表示目的overview
compactNoOptimize copy and layout for ChatGPT mobile/compact views
prefectureNo都道府県名(和名/英名/ISO 3166-2 コード対応)愛知県

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYes
modeYes
layerYes
titleYes
intentYes
summaryYes
prefectureYes
attributionYes
nextActionsYes
dashboardUriYesMCP Apps ui:// resource URI
dashboardUrlYesBrowser fallback URL or path
markdownReportYesCompact markdown fallback for non-UI clients
Behavior4/5

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

Annotations indicate readOnly and non-destructive behavior. The description adds context about output format (map, charts, next actions, markdown fallback) and mobile optimization, which are not in annotations.

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 sentences efficiently cover purpose, components, usage guidance, and multilingual support. Slightly repetitive ('ChatGPT-optimized' appears twice) but overall compact.

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?

Given 5 optional parameters and existence of output schema, the description covers core functionality and usage scenarios. No critical omissions identified.

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 100% with clear parameter descriptions. The tool description does not add significant meaning beyond what the schema already provides for parameters.

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?

The description clearly states it renders a ChatGPT-optimized real estate visual summary with specific components (map, charts, next actions). It distinguishes from sibling analytical tools by focusing on visualization and summarization.

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?

Explicitly specifies when to use (show, visualize, compare, continue) with strong positive guidance. Lacks explicit exclusions but the context of sibling tools makes the usage clear.

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