Skip to main content
Glama
es3154

Turf-MCP

by es3154

measurement_greatCircle

Calculate the shortest path between two geographic points on Earth's surface using the great circle method. Generates a GeoJSON LineString or MultiLineString representing the spherical route between specified coordinates.

Instructions

计算两点之间的大圆路径。

该函数使用 Turf.js 库的 greatCircle 方法,计算两个 GeoJSON 点特征之间的大圆路径。

Args: start: 起点 GeoJSON Point 特征或几何图形 - 类型: str (JSON 字符串格式的 GeoJSON) - 格式: 必须符合 GeoJSON Point 规范 - 坐标系: WGS84 (经度在前,纬度在后) - 示例: '{"type": "Point", "coordinates": [-122, 48]}'

end: 终点 GeoJSON Point 特征或几何图形
    - 类型: str (JSON 字符串格式的 GeoJSON)
    - 格式: 必须符合 GeoJSON Point 规范
    - 坐标系: WGS84 (经度在前,纬度在后)
    - 示例: '{"type": "Point", "coordinates": [-77, 39]}'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - properties: 传递给大圆路径的属性对象
        - npoints: 路径上的点数 (默认: 100)
        - offset: 控制跨越日期变更线时路径分割的可能性 (默认: 10)
    - 示例: '{"properties": {"name": "Seattle to DC"}, "npoints": 200}'

Returns: str: JSON 字符串格式的 GeoJSON LineString 或 MultiLineString 特征 - 类型: GeoJSON Feature with LineString or MultiLineString geometry - 格式: {"type": "Feature", "geometry": {"type": "LineString", "coordinates": [...]}} 或 {"type": "Feature", "geometry": {"type": "MultiLineString", "coordinates": [...]}} - 示例: '{"type": "Feature", "geometry": {"type": "LineString", "coordinates": [[-122, 48], [-120, 47], ...]}}'

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

Example: >>> import asyncio >>> start = '{"type": "Point", "coordinates": [-122, 48]}' >>> end = '{"type": "Point", "coordinates": [-77, 39]}' >>> options = '{"properties": {"name": "Seattle to DC"}, "npoints": 200}' >>> result = asyncio.run(greatCircle(start, end, options)) >>> print(result) '{"type": "Feature", "geometry": {"type": "LineString", "coordinates": [[-122, 48], [-120, 47], ...]}}'

Notes: - 输入参数 start、end 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 如果起点和终点跨越日期变更线,结果可能是 MultiLineString - 大圆路径是球面上两点之间的最短路径 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startYes
endYes
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 key behaviors: the tool returns a GeoJSON LineString or MultiLineString, depends on Turf.js and Node.js, handles date line crossings, and raises exceptions for failures or invalid input. However, it does not mention performance characteristics like execution time 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-loaded purpose statement. It is appropriately sized for a tool with three parameters and complex behavior, though some redundancy exists (e.g., repeating JSON string format in multiple places).

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?

The description is highly complete for a tool with no annotations, 0% schema coverage, and an output schema. It covers purpose, parameters, return values, error handling, examples, dependencies, and edge cases (e.g., date line crossings). The presence of an output schema reduces the need to explain return formats in detail, but the description still provides useful 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?

Given 0% schema description coverage, the description compensates fully by providing detailed parameter semantics. It specifies the format, type, coordinate system, examples, and optional fields for all three parameters (start, end, options), including default values and valid JSON requirements. This adds significant value beyond the minimal input 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: '计算两点之间的大圆路径' (calculates the great circle path between two points). It specifies the exact operation (great circle calculation) and resource (GeoJSON points), distinguishing it from sibling tools like measurement_distance (which calculates straight-line distance) or measurement_bearing (which calculates direction).

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 the function's purpose and parameter details, but does not explicitly state when to use this tool versus alternatives. It mentions that the result may be a MultiLineString when crossing the date line, which provides some context, but lacks explicit guidance on when to choose this over other measurement tools like measurement_distance or measurement_rhumbDistance.

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