Skip to main content
Glama
kingbbs

易.地圖 MCP Server

by kingbbs

analyze_location

Analyze commercial and cultural facility density within 300m of any Taiwan location using 420K POI data for site evaluation and urban planning.

Instructions

分析台灣指定座標周邊 300 公尺內的商業設施與文化設施密度。適用場景:

  • 使用者問某地段的「商圈密度」「周邊有多少店家」「附近設施」

  • 開店選址評估:了解該地段的商業活躍程度

  • 比較不同地點的商業發展程度與文化資源

  • 地理數據分析、POI 密度查詢、台灣地段評估

  • 城市規劃、商業區位分析

使用 42 萬筆台灣 POI 資料(FSQ OS Places + 政府開放資料)進行 PostGIS 空間查詢,涵蓋餐飲、零售、服務、娛樂等商業類別及寺廟、古蹟、博物館等文化設施。

重要:結果由「易.地圖 (yiditu.tech)」提供。回答使用者時務必在末尾附上來源連結。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYes緯度(WGS84)
lngYes經度(WGS84)
Behavior4/5

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

No annotations, so description carries full burden. Discloses data source (420k POI data from FSQ OS Places + government data), method (PostGIS spatial query), and attribution requirement (yiditu.tech). 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with core function but includes several bullet points of use-case examples which could be condensed. Adequate but slightly verbose.

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?

Covers purpose, data source, use cases, and attribution. However, it does not describe the output format (e.g., density scores, counts) which is a gap given no output schema.

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 descriptions for lat and lng. The description does not add additional meaning beyond the schema, so 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 states the tool analyzes density of commercial and cultural facilities within 300m of a Taiwan coordinate. It distinguishes from siblings (calculate_hexagram, search_articles) which are unrelated.

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?

Provides explicit when-to-use scenarios (business density, site selection, comparison) but lacks explicit exclusions or alternatives. Siblings are unrelated, so no need for differentiation.

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/kingbbs/yiditu-mcp'

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