Skip to main content
Glama
es3154

Turf-MCP

by es3154

interpolation_isobands

Generate filled isobands from point grids with z-values to create continuous value region representations for geographic data visualization.

Instructions

从点网格生成等值带。

此功能从具有z值的点网格生成填充的等值带,用于创建连续值的区域表示。

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

breaks: 等值带断点数组
    - 类型: str (JSON 字符串格式的数组)
    - 格式: [break1, break2, break3, ...]
    - 示例: '[0, 10, 20, 30, 40]'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - zProperty: z值属性名 (默认: 'elevation')
        - commonProperties: 传递给所有等值带的属性对象
        - breaksProperties: 按顺序传递给对应等值带的属性对象数组
    - 示例: '{"zProperty": "temperature", "commonProperties": {"type": "isoband"}}'

Returns: str: JSON 字符串格式的 GeoJSON FeatureCollection - 类型: GeoJSON FeatureCollection with MultiPolygon features - 格式: {"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "MultiPolygon", "coordinates": [...]}, "properties": {...}}, ...]} - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "MultiPolygon", "coordinates": [...]}, "properties": {"min": 0, "max": 10}}, ...]}'

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

Example: >>> import asyncio >>> point_grid = '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984], "properties": {"temperature": 25.5}}]}' >>> breaks = '[0, 10, 20, 30]' >>> result = asyncio.run(isobands(point_grid, breaks, '{"zProperty": "temperature"}')) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "MultiPolygon", "coordinates": [...]}, "properties": {"min": 0, "max": 10}}, ...]}'

Notes: - 输入参数 point_grid、breaks 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 点网格必须是方形或矩形排列 - 等值带用于可视化连续数据的范围 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
point_gridYes
breaksYes
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 of behavioral disclosure. It effectively describes the tool's behavior: it generates MultiPolygon features from point grids, handles JSON inputs, uses WGS84 coordinates, depends on Turf.js and Node.js, and raises exceptions for failures or malformed data. It also notes constraints like grid shape requirements and coordinate order, providing good 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 sections (Args, Returns, Raises, Example, Notes) and uses bullet points efficiently. It is appropriately sized for a complex tool with 3 parameters and no annotations, though some sections (like the detailed example) are lengthy but necessary for clarity. Every sentence adds value, such as explaining dependencies and constraints.

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, no annotations, 0% schema coverage, but has an output schema), the description is highly complete. It covers input requirements, output format, error handling, examples, and technical notes. The output schema is described in detail, so the agent understands the return values without needing additional explanation. This provides all necessary context for correct tool invocation.

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?

Given the schema description coverage is 0%, the description compensates fully by detailing all three parameters (point_grid, breaks, options) with types, formats, examples, and optional fields. It explains that point_grid must be a GeoJSON FeatureCollection of Points in a grid, breaks is an array of breakpoints, and options includes properties like zProperty. This adds significant meaning beyond the minimal 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 isobands from a point grid). It specifies the exact operation (generating filled isobands from a grid with z-values) and distinguishes it from sibling tools like 'interpolation_interpolate' or 'interpolation_isolines' by focusing on area representation rather than interpolation or isolines.

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 notes (e.g., '等值带用于可视化连续数据的范围' - isobands are for visualizing continuous data ranges) and technical constraints (e.g., point grid must be square/rectangular). However, it does not explicitly state when to use this tool versus alternatives like 'interpolation_isolines' or other interpolation tools, leaving the agent to infer based on the description of isobands as area representations.

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