japan-real-estate-intel

Overview Schema Related Servers Score Discussions

日照・景観シミュレーション

simulate_landscape_impact

Read-onlyIdempotent

Simulate sunlight and shadow patterns at any location using 3D building data to assess landscape impact from surrounding structures.

Instructions

Sunlight/shadow simulation using PLATEAU 3D buildings + SunCalc. | 日照・影シミュレーション。PLATEAU 3D建物データ+SunCalcで周辺建物の影響を分析。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	Yes	対象地点の緯度
`lng`	Yes	対象地点の経度
`radiusM`	No	建物検索半径（メートル）
`dateTime`	No	シミュレーション日時（ISO 8601形式、省略時は現在時刻）
`prefecture`	No	都道府県名（和名/英名/ISO 3166-2 コード対応）	愛知県
`timePreset`	No	時刻プリセット（morning=8:00, noon=12:00, evening=17:00）
`includeMarkdown`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`avgHeight`	Yes
`maxHeight`	Yes
`keyInsights`	Yes
`sunPosition`	Yes
`markdownReport`	No
`shadowPolygons`	Yes
`totalShadowAreaSqm`	Yes
`highImpactBuildings`	Yes
`nearbyBuildingCount`	Yes
`sunlightHoursEstimate`	Yes

Schema Changelog

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

Changed1 schema field changedv8.0.0Jul 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "avgHeight": {
+      "type": "number"
+    },
+    "highImpactBuildings": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "distance": {
+            "type": "number"
+          },
+          "height": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "height",
+          "distance"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "keyInsights": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "markdownReport": {
+      "type": "string"
+    },
+    "maxHeight": {
+      "type": "number"
+    },
+    "nearbyBuildingCount": {
+      "type": "number"
+    },
+    "shadowPolygons": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "buildingName": {
+            "type": "string"
+          },
+          "height": {
+            "type": "number"
+          },
+          "polygon": {
+            "items": {
+              "items": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "number"
+                }
+              ],
+              "type": "array"
+            },
+            "type": "array"
+          },
+          "shadowLengthM": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "buildingName",
+          "height",
+          "shadowLengthM",
+          "polygon"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sunPosition": {
+      "additionalProperties": false,
+      "properties": {
+        "altitudeDeg": {
+          "type": "number"
+        },
+        "azimuthDeg": {
+          "type": "number"
+        },
+        "dateTime": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "azimuthDeg",
+        "altitudeDeg",
+        "dateTime"
+      ],
+      "type": "object"
+    },
+    "sunlightHoursEstimate": {
+      "type": "number"
+    },
+    "totalShadowAreaSqm": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "sunPosition",
+    "nearbyBuildingCount",
+    "maxHeight",
+    "avgHeight",
+    "totalShadowAreaSqm",
+    "sunlightHoursEstimate",
+    "shadowPolygons",
+    "highImpactBuildings",
+    "keyInsights"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv7.0.0Jul 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv6.16.0May 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds behavioral context beyond annotations: specifies data sources and analysis scope (surrounding buildings). No contradiction with readOnlyHint/idempotentHint/destructiveHint.

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 concise sentences, bilingual. Slightly repetitive but no fluff. Efficient.

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?

Adequate for core purpose, but could mention need for internet access to fetch PLATEAU data. Output schema exists, so no need to describe returns.

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 86%, above 80% baseline. Description does not add extra parameter-specific details beyond 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 clearly states the tool simulates sunlight/shadow using PLATEAU 3D buildings and SunCalc. Distinguishes from siblings like 'scenario_what_if' or 'assess_exterior_visuals'.

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?

Implied usage for sunlight/shadow analysis but no explicit when-to-use or when-not-to-use guidance. No alternatives mentioned.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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