Skip to main content
Glama
sugukurukabe

japan-real-estate-intel

AI外観監査

assess_exterior_visuals
Read-onlyIdempotent

AI-powered exterior audit of Japanese properties using Street View and Vision AI to assess building appearance, road width, and environment. Provides visual assessment results even without API keys.

Instructions

AI visual exterior audit of a property using the Google Maps Street View Static API (https://developers.google.com/maps/documentation/streetview) and Google Gemini Vision (https://ai.google.dev/gemini-api/docs/vision) for image analysis. Falls back to a simulated audit if GOOGLE_MAPS_API_KEY/GOOGLE_GENAI_API_KEY are not configured. | AI街頭外観監査。Google Maps Street View Static APIとGemini Vision AIを用いて建物の外観・道路幅・環境を自動評価。APIキー未設定時はシミュレーション結果にフォールバック。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo市区町村(例: '名古屋市中村区'、'世田谷区')
pitchNoカメラの上下角 (-90=真下、0=水平、90=真上)
addressNo詳細な住所または建物名(例: '名駅南1丁目3-9')
headingNoカメラの向き (0=北、90=東、180=南、270=西)
latitudeNo緯度
longitudeNo経度
prefectureNo都道府県名(和名/英名/ISO 3166-2 コード対応)愛知県

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
analysisYes
imageUrlYes取得またはモックされたストリートビュー画像のURL (または Base64 埋め込み)
latitudeYes
longitudeYes
attributionYes
hasLiveImageYesGoogle Street View APIからライブ画像を取得できたか
markdownReportYesMarkdown形式の詳細レポート
hasLiveAnalysisYesGemini Vision APIによるライブ画像画像解析が行われたか
Behavior4/5

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

Annotations already indicate safe, idempotent, non-destructive behavior. The description adds value by disclosing the reliance on specific external APIs and the fallback to simulated results when keys are unconfigured, providing important context beyond 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?

The description is concise with two sentences, front-loading the core purpose. The second sentence adds important fallback context. No unnecessary words.

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 the tool's complexity (7 parameters, no required, output schema present), the description adequately covers purpose, API dependencies, and fallback behavior. It provides sufficient context for an AI agent to understand the tool's capabilities.

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 each parameter having clear descriptions. The description does not add significant new meaning beyond noting the use of Street View (which relates to heading/pitch) and Gemini. Baseline 3 is appropriate.

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 specifies the tool's purpose: an AI visual exterior audit using Google Maps Street View and Gemini Vision. It identifies the resource (property exterior) and the action (assess), and distinguishes itself from siblings by mentioning the use of specific APIs and fallback simulation.

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?

The description implies usage when an exterior visual audit is needed and mentions fallback behavior when API keys are missing, but it does not explicitly state when to choose this tool over siblings like quick_visual_summary or assess_family_friendly_score.

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