Skip to main content
Glama
es3154

Turf-MCP

by es3154

misc_line_intersect

Calculate intersection points between two lines or polygons using GeoJSON input. Returns coordinates where geometries cross for spatial analysis.

Instructions

计算两条线的交点。

此功能计算两条线或多边形几何图形之间的交点,返回所有交叉点的位置坐标。

Args: line1: 第一条线 GeoJSON 特征或几何图形 - 类型: str (JSON 字符串格式的 GeoJSON) - 格式: 支持 LineString、MultiLineString、Polygon、MultiPolygon - 坐标系: WGS84 (经度在前,纬度在后) - 示例: '{"type": "LineString", "coordinates": [[126, -11], [129, -21]]}'

line2: 第二条线 GeoJSON 特征或几何图形
    - 类型: str (JSON 字符串格式的 GeoJSON)
    - 格式: 支持 LineString、MultiLineString、Polygon、MultiPolygon
    - 坐标系: WGS84 (经度在前,纬度在后)
    - 示例: '{"type": "LineString", "coordinates": [[123, -18], [131, -14]]}'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - removeDuplicates: 是否移除重复交点 (默认: true)
        - ignoreSelfIntersections: 是否忽略自相交点 (默认: true)
    - 示例: '{"removeDuplicates": true, "ignoreSelfIntersections": true}'

Returns: str: JSON 字符串格式的点特征集合 - 类型: GeoJSON FeatureCollection with Point features - 格式: {"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [lng, lat]}}, ...]}

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

Example: >>> import asyncio >>> line1 = '{"type": "LineString", "coordinates": [[126, -11], [129, -21]]}' >>> line2 = '{"type": "LineString", "coordinates": [[123, -18], [131, -14]]}' >>> result = asyncio.run(line_intersect(line1, line2)) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [127.5, -16]}}]}'

Notes: - 输入参数 line1 和 line2 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 返回两条线之间的所有交点 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
line1Yes
line2Yes
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 and does an excellent job. It clearly explains what the tool does (returns all intersection points), discloses dependencies (Turf.js and Node.js environment), error conditions (JavaScript execution failures, timeouts, input format errors), and output format. The only minor gap is lack of information about performance characteristics or rate limits.

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 clear sections (Args, Returns, Raises, Example, Notes) and front-loads the core purpose. While comprehensive, some information could be more concise - the parameter documentation is quite detailed, and the example includes unnecessary import statements. However, every sentence adds value, and the structure helps navigation.

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 (geometric calculations with multiple parameter types), no annotations, and 0% schema coverage, the description provides exceptional completeness. It covers purpose, parameters, return values, error conditions, dependencies, coordinate systems, and includes a working example. The presence of an output schema helps, but the description still provides valuable context about the GeoJSON format and specific return structure.

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 comprehensive parameter documentation. Each parameter (line1, line2, options) gets detailed explanations including types, formats, coordinate systems, examples, and for options - specific fields with defaults. This goes far beyond what the bare schema provides and gives the agent complete understanding of how to use the parameters correctly.

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 ('计算两条线的交点' - calculates intersection points of two lines) and resources (GeoJSON features/geometries). It distinguishes itself from siblings by focusing specifically on line intersection calculation, unlike other tools like 'booleans_booleanCrosses' or 'transformation_intersect' which handle different geometric operations.

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 about when to use this tool (for calculating intersection points between lines/polygons) and includes technical prerequisites (valid JSON strings, WGS84 coordinate system). However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the many sibling tools, which prevents a perfect score.

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