Skip to main content
Glama
es3154

Turf-MCP

by es3154

random_randomPolygon

Generate random polygon features within specified bounding boxes for geospatial testing and data simulation. Create customizable polygon collections with control over count, vertices, and spatial boundaries.

Instructions

生成随机多边形特征集合。

此功能在指定边界框内生成指定数量的随机多边形,返回多边形特征集合。

Args: count: 生成多边形的数量 - 类型: int - 默认: 1 - 示例: 25

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - bbox: 边界框数组 [minX, minY, maxX, maxY] (默认: [-180, -90, 180, 90])
        - num_vertices: 每个多边形的顶点数量 (默认: 10)
        - max_radial_length: 顶点距离多边形中心的最大径向长度 (默认: 10)
    - 示例: '{"bbox": [-180, -90, 180, 90], "num_vertices": 10}'

Returns: str: JSON 字符串格式的 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": [[[125, -15], [113, -22], [154, -27], [144, -15], [125, -15]]]}}, ...]}'

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

Example: >>> import asyncio >>> result = asyncio.run(randomPolygon(25)) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[125, -15], [113, -22], [154, -27], [144, -15], [125, -15]]]}}, ...]}'

Notes: - 输入参数 options 必须是有效的 JSON 字符串或 None - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 如果未指定边界框,默认在全球范围内生成随机多边形 - 多边形会自动闭合,首尾坐标点相同 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
optionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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. It discloses key behaviors: it returns GeoJSON FeatureCollection, uses WGS84 coordinates, auto-closes polygons, has a global default bbox, and depends on Turf.js/Node.js. It also mentions error conditions (JavaScript failures, timeouts, input errors). However, it does not cover rate limits or authentication needs, though these may not apply.

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 sections (Args, Returns, Raises, Example, Notes), making it easy to navigate. It is appropriately sized but could be more front-loaded; the core purpose is stated first, but some details are buried in notes. Most sentences earn their place, though the example is lengthy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (generating random polygons with configurable parameters), no annotations, 0% schema coverage, and an output schema provided, the description is highly complete. It covers purpose, parameters, return format, errors, examples, and notes on dependencies and defaults, leaving no significant gaps for the agent.

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 compensate. It fully documents both parameters: 'count' with type, default, and example, and 'options' with type, optional fields (bbox, num_vertices, max_radial_length), defaults, examples, and validation rules (must be valid JSON or None). This adds significant meaning beyond the basic 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 tool's purpose: '生成随机多边形特征集合' (generate random polygon feature collection). It specifies the verb ('生成' - generate) and resource ('随机多边形特征集合' - random polygon feature collection), and distinguishes it from sibling tools like random_randomPoint or random_randomLineString by focusing on polygons.

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 by detailing parameters like count and options, but does not explicitly state when to use this tool versus alternatives. It mentions dependencies (Turf.js, Node.js) and coordinate system (WGS84), which provide some context, but lacks explicit guidance on scenarios or comparisons with siblings.

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