Skip to main content
Glama
es3154

Turf-MCP

by es3154

measurement_bboxPolygon

Convert bounding box coordinates to GeoJSON polygon features for spatial analysis and visualization. This tool transforms rectangular bounding boxes into polygon geometry for use in mapping applications and geospatial operations.

Instructions

将边界框转换为多边形特征。

此功能将边界框坐标转换为完整的多边形几何图形,便于进行多边形操作和可视化。

Args: bbox: 边界框数组 - 类型: str (JSON 字符串格式的数组) - 格式: [minX, minY, maxX, maxY] - 示例: '[-82, 35, -74, 42]'

options: 可选参数配置
    - 类型: str (JSON 字符串) 或 None
    - 可选字段:
        - properties: 传递给多边形的属性对象
        - id: 传递给多边形的 ID
    - 示例: '{"properties": {"name": "bounding box"}, "id": "bbox1"}'

Returns: str: JSON 字符串格式的 GeoJSON Polygon 特征 - 类型: GeoJSON Feature with Polygon geometry - 格式: {"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [...]}} - 示例: '{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[-82, 35], [-74, 35], [-74, 42], [-82, 42], [-82, 35]]]}}'

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

Example: >>> import asyncio >>> bbox = '[-82, 35, -74, 42]' >>> options = '{"properties": {"name": "bounding box"}}' >>> result = asyncio.run(bboxPolygon(bbox, options)) >>> print(result) '{"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[-82, 35], [-74, 35], [-74, 42], [-82, 42], [-82, 35]]]}}'

Notes: - 输入参数 bbox 和 options 必须是有效的 JSON 字符串 - 边界框格式为 [minX, minY, maxX, maxY] - 坐标顺序为 [经度, 纬度] (WGS84 坐标系) - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bboxYes
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 at disclosing behavioral traits. It specifies input format requirements (JSON strings), coordinate system (WGS84), dependencies (Turf.js, Node.js), error conditions (JavaScript execution failure, timeout, data format errors), and output format (GeoJSON Polygon feature). It doesn't mention performance characteristics like rate limits, 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 clear sections (Args, Returns, Raises, Example, Notes) and front-loaded purpose statement. While comprehensive, some sections could be more concise - the example includes full import and execution code that might be simplified. Overall, most sentences earn their place by providing valuable 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 (coordinate transformation), lack of annotations, and 0% schema coverage, the description provides complete context. It explains inputs, outputs (though an output schema exists), error conditions, dependencies, coordinate systems, and includes a working example. The description successfully compensates for the lack of structured metadata.

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. It explains both parameters (bbox and options) with type information, format specifications, examples, and optional fields for options. The description adds comprehensive meaning beyond the minimal input schema, making parameter usage clear.

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 verb ('将边界框转换为' - converts bounding box to) and resource ('多边形特征' - polygon feature), distinguishing it from sibling tools like 'measurement_bbox' (which likely measures bounding boxes) or 'feature_conversion_polygonize' (which creates polygons from other geometries). The purpose is precise and unambiguous.

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 ('便于进行多边形操作和可视化' - facilitates polygon operations and visualization), but doesn't explicitly state when not to use it or name specific alternatives among the many sibling tools. The context is helpful but lacks explicit exclusion criteria or comparison to similar tools like 'feature_conversion_line_to_polygon'.

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