Skip to main content
Glama
es3154

Turf-MCP

by es3154

aggregation_clustersKmeans

Groups geographic points into clusters using the K-means algorithm to organize spatial data into specified categories for analysis.

Instructions

使用 K-means 算法进行点聚类。

此功能使用 K-means 聚类算法对点进行聚类,将点划分为指定数量的簇。

Args: points: 点特征集合 - 类型: str (JSON 字符串格式的 GeoJSON FeatureCollection) - 格式: FeatureCollection with Point features - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}}, ...]}'

number_of_clusters: 聚类数量
    - 类型: int
    - 描述: 要创建的聚类数量
    - 示例: 5

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - numberOfClusters: 聚类数量(与 number_of_clusters 参数相同)
        - mutate: 是否修改原始特征 (默认: false)
    - 示例: '{"mutate": true}'

Returns: str: JSON 字符串格式的 GeoJSON FeatureCollection - 类型: GeoJSON FeatureCollection with Point features - 格式: {"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [lng, lat]}, "properties": {"cluster": 聚类编号, ...}}, ...]} - 示例: '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}, "properties": {"cluster": 1}}, ...]}'

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

Example: >>> import asyncio >>> points = '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}}]}' >>> result = asyncio.run(clustersKmeans(points, 5)) >>> print(result) '{"type": "FeatureCollection", "features": [{"type": "Feature", "geometry": {"type": "Point", "coordinates": [-75.343, 39.984]}, "properties": {"cluster": 1}}, ...]}'

Notes: - 输入参数 points 和 options 必须是有效的 JSON 字符串 - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - K-means 算法需要预先指定聚类数量 - 聚类编号从 0 开始 - 算法使用随机初始中心点,每次运行结果可能不同 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes
number_of_clustersYes
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 full burden and does well. It discloses important behavioral traits: algorithm uses random initialization (results may vary), cluster numbering starts at 0, coordinate system (WGS84), dependencies (Turf.js, Node.js), and error conditions (JavaScript execution failures, timeouts, format errors). It also mentions the 'mutate' option that can modify original features.

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 sections like the detailed example could be slightly condensed. Most sentences earn their place by providing essential information.

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 (clustering algorithm with 3 parameters), no annotations, and the presence of an output schema, the description is remarkably complete. It covers purpose, parameters, return format, errors, example usage, and important behavioral notes. The output schema existence means the description doesn't need to explain return values in detail, which it respects while still providing helpful 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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. Each parameter (points, number_of_clusters, options) gets comprehensive explanations including types, formats, examples, and for 'options', the specific optional fields. The description adds substantial meaning 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 specific action ('使用 K-means 算法进行点聚类' - uses K-means algorithm for point clustering) and resource ('点' - points). It distinguishes from sibling tools like 'aggregation_clustersDbscan' by specifying the algorithm used (K-means vs DBSCAN). The purpose is unambiguous and algorithm-specific.

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 for when to use this tool (clustering points with K-means algorithm) and mentions it requires pre-specified cluster count. However, it doesn't explicitly state when NOT to use it or compare it with alternatives like the DBSCAN sibling tool, which would be helpful for algorithm selection.

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