Skip to main content
Glama
es3154

Turf-MCP

by es3154

interpolation_tin

Create irregular triangular networks from point data for surface modeling and terrain analysis. Generate continuous terrain models by connecting elevation points into triangular polygons.

Instructions

从点集创建不规则三角网。

此功能从点集创建不规则三角网,用于表面建模和地形分析。

Args: points: 点特征集合 - 类型: str (JSON 字符串格式的 GeoJSON FeatureCollection) - 格式: FeatureCollection with Point features - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984], "properties": {"elevation": 100}}, ...]}'

z_property: z值属性名
    - 类型: str 或 None
    - 描述: 用于z值的属性名,如果为None则不添加额外数据
    - 示例: 'elevation'

Returns: str: JSON 字符串格式的 GeoJSON FeatureCollection - 类型: GeoJSON FeatureCollection with Polygon features - 格式: {"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [...]}, "properties": {...}}, ...]} - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [...]}, "properties": {"a": 100, "b": 150, "c": 120}}, ...]}'

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

Example: >>> import asyncio >>> points = '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984], "properties": {"elevation": 100}}]}' >>> result = asyncio.run(tin(points, 'elevation')) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [...]}, "properties": {"a": 100, "b": 150, "c": 120}}, ...]}'

Notes: - 输入参数 points 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 不规则三角网用于创建连续的表面模型 - 每个三角形包含三个顶点的z值属性 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes
z_propertyNo

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 of behavioral disclosure. It effectively describes what the tool does (creates TIN from points), mentions dependencies (Turf.js and Node.js), specifies coordinate system (WGS84 with [longitude, latitude] order), and documents error conditions (JavaScript execution failures, timeouts, input format errors). However, it doesn't mention performance characteristics like computational complexity or memory usage.

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 it's quite lengthy with multiple detailed examples and technical notes. While all content is relevant, it could be more front-loaded with the core purpose. The structure helps navigation but the overall length reduces conciseness.

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 (geospatial triangulation), no annotations, and 0% schema coverage, the description provides comprehensive documentation. It covers purpose, parameters, return format, error conditions, examples, coordinate system, dependencies, and use cases. With an output schema present, the description appropriately focuses on behavioral context rather than repeating return value details.

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, the description fully compensates by providing detailed parameter documentation. It explains both parameters thoroughly: 'points' as a GeoJSON FeatureCollection string with format details and examples, and 'z_property' as an optional attribute name for elevation data with clear examples. The description adds significant value 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 tool's purpose: '从点集创建不规则三角网' (create an irregular triangular network from point sets). It specifies the exact action (创建/create) and resource (不规则三角网/irregular triangular network), and distinguishes from siblings by mentioning its use for surface modeling and terrain analysis, unlike other interpolation tools like 'interpolation_interpolate' or 'interpolation_isolines'.

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?

The description provides clear context for when to use this tool: for surface modeling and terrain analysis using point sets. It doesn't explicitly state when not to use it or name alternatives among siblings, but the specific application context is well-defined, making it clear this is for triangulation tasks rather than other interpolation methods.

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