Skip to main content
Glama
es3154

Turf-MCP

by es3154

helper_feature

Create GeoJSON features by combining geometry and attribute data for geographic representation in spatial analysis workflows.

Instructions

创建单个地理特征对象。

此功能将几何图形和属性信息组合成一个完整的地理特征,用于表示具体的地理要素。

Args: geometry: 几何图形对象 - 类型: str (JSON 字符串格式的 GeoJSON 几何图形) - 格式: 任何有效的 GeoJSON 几何图形 - 示例: '{"type": "Point", "coordinates": [-75.343, 39.984]}'

properties: 属性对象
    - 类型: str (JSON 字符串) 或 None
    - 格式: 键值对对象
    - 示例: '{"name": "Location A", "type": "landmark"}'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - bbox: 边界框数组 [minX, minY, maxX, maxY]
        - id: 特征的标识符
    - 示例: '{"bbox": [-75.5, 39.5, -75, 40], "id": "feature1"}'

Returns: str: JSON 字符串格式的 GeoJSON Feature - 类型: GeoJSON Feature - 格式: {"type": "Feature", "geometry": {...}, "properties": {...}} - 示例: '{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}, "properties": {"name": "Location A"}}'

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

Example: >>> import asyncio >>> geometry = '{"type": "Point", "coordinates": [-75.343, 39.984]}' >>> properties = '{"name": "Location A"}' >>> result = asyncio.run(feature(geometry, properties)) >>> print(result) '{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}, "properties": {"name": "Location A"}}'

Notes: - 输入参数 geometry、properties 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 特征是 GeoJSON 中的基本数据单元,包含几何信息和属性 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geometryYes
propertiesNo
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 full burden. It discloses several behavioral traits: it creates a complete geographic feature (not just geometry), requires valid JSON strings as input, uses WGS84 coordinate system with [longitude, latitude] order, returns a GeoJSON Feature string, raises exceptions for execution failures/timeouts/format errors, and depends on Turf.js and Node.js. It doesn't mention performance characteristics or rate limits, but covers core behavior well.

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?

The description is well-structured with clear sections (Args, Returns, Raises, Example, Notes), but is quite lengthy with detailed parameter explanations and a full code example. While informative, it could be more concise by reducing some redundancy (e.g., the example repeats format details). Every sentence adds value, but front-loading could be improved.

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 (3 parameters, 0% schema coverage, no annotations, but has output schema), the description is highly complete. It covers purpose, parameters, return values (though output schema exists, it adds clarity), error conditions, dependencies, coordinate system, and provides a working example. For a creation tool with no annotations, this provides comprehensive context.

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?

With 0% schema description coverage (schema only provides types without descriptions), the description fully compensates by providing detailed parameter semantics. It explains each parameter's purpose, format requirements, optional fields, and provides concrete examples. The description adds significant value beyond the bare schema, making parameter usage clear.

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: '创建单个地理特征对象' (create a single geographic feature object). It specifies the verb ('创建' - create) and resource ('地理特征对象' - geographic feature object), and distinguishes from siblings like 'helper_featureCollection' (which creates collections) and geometry helpers (which create only geometry).

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 mentioning it's for '表示具体的地理要素' (representing specific geographic elements) and that features are 'GeoJSON 中的基本数据单元' (basic data units in GeoJSON). However, it doesn't explicitly state when to use this vs. alternatives like 'helper_featureCollection' for multiple features or geometry helpers for geometry-only creation. No explicit exclusions or prerequisites are provided.

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