Skip to main content
Glama
es3154

Turf-MCP

by es3154

transformation_voronoi

Generate Voronoi polygons from point data to partition geographic space into regions based on proximity to input points.

Instructions

生成 Voronoi 多边形。

该函数使用 Turf.js 库的 voronoi 方法,从点集生成 Voronoi 多边形。

Args: points: 点集 GeoJSON FeatureCollection - 类型: str (JSON 字符串格式的 GeoJSON) - 格式: 必须符合 GeoJSON FeatureCollection 规范,包含 Point 特征 - 坐标系: WGS84 (经度在前,纬度在后) - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}}, ...]}'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - bbox: 裁剪矩形边界框 (默认: [-180,-85,180,-85])
    - 示例: '{"bbox": [-70, 40, -60, 60]}'

Returns: str: JSON 字符串格式的 Voronoi 多边形集合 GeoJSON FeatureCollection - 类型: GeoJSON FeatureCollection with Polygon features - 格式: {"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [...]}}]} - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[-75.35, 39.98], [-75.34, 39.99], ...]]}}, ...]}'

Raises: Exception: 当 JavaScript 执行失败、超时或输入数据格式错误时抛出异常

Example: >>> import asyncio >>> points = '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}}]}' >>> options = '{"bbox": [-70, 40, -60, 60]}' >>> result = asyncio.run(voronoi(points, options)) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[-75.35, 39.98], [-75.34, 39.99], ...]]}}, ...]}'

Notes: - 输入参数 points 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 算法来自 d3-voronoi 包 - 每个输入点对应一个输出多边形 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes
optionsNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the tool generates Voronoi polygons from point sets, specifies coordinate system (WGS84), mentions each input point corresponds to an output polygon, and notes dependencies (Turf.js, Node.js). It also covers error conditions (Raises section) and technical constraints (e.g., JSON string format, coordinate order). This provides substantial behavioral context beyond basic functionality.

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 well-structured with clear sections (Args, Returns, Raises, Example, Notes), making it easy to navigate. It is appropriately sized for a tool with technical complexity, though some sections (like the detailed example) are lengthy. Most sentences earn their place by providing essential technical details, but it could be slightly more concise in the example section.

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 (geometric transformation with specific input/output formats), no annotations, and no output schema, the description does an excellent job of providing context. It covers input requirements, output format, error handling, dependencies, and examples. The only minor gap is the lack of explicit usage guidelines versus alternatives, but overall it is highly complete for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully compensate. It provides detailed semantic information for both parameters: 'points' is explained as a GeoJSON FeatureCollection with Point features in WGS84, including format, coordinate order, and an example; 'options' is described as optional with a 'bbox' field for clipping, including default values and an example. This adds comprehensive meaning beyond the bare 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?

The description clearly states the specific action ('生成 Voronoi 多边形' - generate Voronoi polygons) and resource ('从点集' - from point sets). It distinguishes itself from sibling tools by specifying the geometric transformation it performs, unlike other transformation tools like buffer, simplify, or union. The purpose is precise and unambiguous.

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 context through technical details (e.g., input format, coordinate system, algorithm source), but does not explicitly state when to use this tool versus alternatives. It mentions the algorithm is from d3-voronoi and depends on Turf.js/Node.js, which provides some technical context, but lacks explicit guidance on scenarios or comparisons with sibling tools.

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/es3154/turf-mcp'

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