Skip to main content
Glama
es3154

Turf-MCP

by es3154

misc_line_slice_along

Extract a segment of a line between specified distances from its start point. This tool helps users isolate specific portions of linear features for spatial analysis or visualization.

Instructions

沿线段长度截取指定距离范围的部分。

此功能根据起点距离和终点距离在线段上截取对应的部分,便于按长度分割线段。

Args: line: 线 GeoJSON 特征或几何图形 - 类型: str (JSON 字符串格式的 GeoJSON) - 格式: 必须符合 GeoJSON LineString 规范 - 坐标系: WGS84 (经度在前,纬度在后) - 示例: '{"type": "LineString", "coordinates": [[7, 45], [9, 45], [14, 40], [14, 41]]}'

start_distance: 起点距离
    - 类型: float
    - 描述: 从线段起点开始的截取起始距离
    - 示例: 12.5

stop_distance: 终点距离
    - 类型: float
    - 描述: 从线段起点开始的截取结束距离
    - 示例: 25.0

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - units: 距离单位 (默认: 'kilometers')
            - 有效值: 'miles', 'nauticalmiles', 'kilometers', 'meters', 'yards', 'feet', 'inches'
    - 示例: '{"units": "miles"}'

Returns: str: JSON 字符串格式的 GeoJSON LineString 特征 - 类型: GeoJSON Feature with LineString geometry - 格式: {"type": "Feature", "geometry": {"type": "LineString", "coordinates": [...]}}

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

Example: >>> import asyncio >>> line = '{"type": "LineString", "coordinates": [[7, 45], [9, 45], [14, 40], [14, 41]]}' >>> options = '{"units": "miles"}' >>> result = asyncio.run(line_slice_along(line, 12.5, 25.0, options)) >>> print(result) '{"type": "Feature", "geometry": {"type": "LineString", "coordinates": [[...]]}}'

Notes: - 输入参数 line 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 根据距离范围截取线段部分 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineYes
start_distanceYes
stop_distanceYes
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 behavioral traits such as input validation requirements (valid JSON strings, WGS84 coordinate order), output format (GeoJSON LineString feature), error conditions (raises Exception on failures), and dependencies (Turf.js and Node.js). However, it does not mention performance aspects like rate limits or computational complexity.

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 for Args, Returns, Raises, Example, and Notes, making it easy to navigate. It is appropriately sized but includes some redundancy (e.g., repeating JSON format details). Most sentences earn their place, though minor trimming could improve 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 moderate complexity (4 parameters, geometric operations), no annotations, and an output schema present, the description is complete. It covers purpose, detailed parameter semantics, output format, error handling, examples, and dependencies, providing all necessary context for an AI agent to use the tool effectively.

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 0% schema description coverage, the description fully compensates by providing detailed semantics for all 4 parameters: 'line' (GeoJSON format, coordinate system, example), 'start_distance' and 'stop_distance' (definitions, examples), and 'options' (optional JSON with units field and valid values). This 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 with specific verbs ('截取' meaning 'slice/extract') and resources ('线段' meaning 'line segment'), specifying it extracts a portion along a line segment based on distance ranges. It distinguishes itself from siblings like 'misc_line_slice' (which might slice based on points) and 'misc_line_segment' (which might create segments differently), making the purpose explicit and differentiated.

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 stating it's for '按长度分割线段' (splitting line segments by length), but does not explicitly say when to use this tool versus alternatives like 'misc_line_slice' or 'misc_line_segment'. It provides context about input formats and dependencies, but lacks explicit guidance on tool selection or exclusions.

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