Skip to main content
Glama
es3154

Turf-MCP

by es3154

helper_multiLineString

Create GeoJSON MultiLineString features from coordinate arrays to represent complex linear elements with multiple independent lines in geospatial applications.

Instructions

创建多线特征对象。

此功能根据多组坐标点数组创建多线特征,用于表示包含多条线的复杂线性要素。

Args: coordinates: 多线坐标数组 - 类型: str (JSON 字符串格式的数组) - 格式: [[[lng1, lat1], [lng2, lat2], ...], [[lng3, lat3], [lng4, lat4], ...]] - 示例: '[[[[-24, 63], [-23, 60], [-25, 65], [-20, 69]]], [[[-14, 43], [-13, 40], [-15, 45], [-10, 49]]]]'

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

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

Returns: str: JSON 字符串格式的 GeoJSON MultiLineString Feature - 类型: GeoJSON Feature with MultiLineString geometry - 格式: {"type": "Feature", "geometry": {"type": "MultiLineString", "coordinates": [...]}, "properties": {...}} - 示例: '{"type": "Feature", "geometry": {"type": "MultiLineString", "coordinates": [[[-24, 63], [-23, 60], ...], [[-14, 43], [-13, 40], ...]]}, "properties": {"name": "multi route"}}'

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

Example: >>> import asyncio >>> coordinates = '[[[[-24, 63], [-23, 60], [-25, 65], [-20, 69]]], [[[-14, 43], [-13, 40], [-15, 45], [-10, 49]]]]' >>> properties = '{"name": "multi route"}' >>> result = asyncio.run(multiLineString(coordinates, properties)) >>> print(result) '{"type": "Feature", "geometry": {"type": "MultiLineString", "coordinates": [...]}, "properties": {"name": "multi route"}}'

Notes: - 输入参数 coordinates、properties 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 多线特征包含多条独立的线 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coordinatesYes
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 the full burden. It discloses key behavioral traits: the tool creates GeoJSON MultiLineString features, requires valid JSON string inputs, uses [longitude, latitude] order in WGS84, includes error handling ('Raises: Exception: 当 JavaScript 执行失败、超时或输入数据格式错误时抛出异常' - raises exceptions for JavaScript execution failure, timeout, or input format errors), and has dependencies on Turf.js and Node.js. It does not cover rate limits, authentication needs, or performance characteristics, but provides substantial operational context.

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 for a tool with three parameters and complex data formats. Some redundancy exists (e.g., repeating JSON string format in multiple places), but overall, sentences earn their place by providing essential details without unnecessary fluff.

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 complexity (3 parameters with 0% schema coverage, no annotations, but has output schema), the description is complete. It explains the tool's purpose, parameters in detail, return format (GeoJSON Feature with MultiLineString geometry), error conditions, dependencies, and includes a full example. The output schema existence means the description doesn't need to redundantly explain return values, but it still provides a clear return example and format, ensuring the agent has all necessary 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?

Schema description coverage is 0%, so the description must fully compensate. It adds comprehensive meaning beyond the schema: for 'coordinates', it specifies the JSON string format, nested array structure with examples, and coordinate order; for 'properties', it describes it as a key-value object JSON string or null with an example; for 'options', it details optional fields (bbox, id) with examples. This fully documents all three parameters with clear semantics and usage examples.

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 multi-line feature object) and elaborates with '根据多组坐标点数组创建多线特征,用于表示包含多条线的复杂线性要素' (create multi-line features based on multiple coordinate point arrays, used to represent complex linear elements containing multiple lines). It distinguishes from siblings like helper_lineString by specifying it handles multiple lines, not single lines.

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 through context (e.g., '用于表示包含多条线的复杂线性要素' - used for complex linear elements with multiple lines) and notes dependencies ('依赖于 Turf.js 库和 Node.js 环境' - depends on Turf.js library and Node.js environment). However, it lacks explicit guidance on when to use this tool versus alternatives like helper_lineString or helper_multiPolygon, and does not specify prerequisites or exclusions beyond format requirements.

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