Skip to main content
Glama
es3154

Turf-MCP

by es3154

unit_conversion_convertArea

Convert area measurements between units like meters, acres, feet, and hectares using this geospatial tool from Turf-MCP.

Instructions

转换面积单位。

此功能将面积值从一种单位转换为另一种单位。

Args: area: 面积值 - 类型: float - 描述: 要转换的面积数值 - 示例: 1000.0

original_unit: 原始单位
    - 类型: str
    - 描述: 输入面积的单位
    - 有效值: 'meters', 'metres', 'centimeters', 'centimetres', 'millimeters', 'millimetres', 'acres', 'miles', 'nauticalmiles', 'inches', 'yards', 'feet', 'kilometers', 'hectares'
    - 示例: 'meters'

final_unit: 目标单位
    - 类型: str
    - 描述: 输出面积的单位
    - 有效值: 'meters', 'metres', 'centimeters', 'centimetres', 'millimeters', 'millimetres', 'acres', 'miles', 'nauticalmiles', 'inches', 'yards', 'feet', 'kilometers', 'hectares'
    - 示例: 'acres'

Returns: str: JSON 字符串格式的面积结果 - 类型: 包含 value 和 units 的对象 - 格式: {"value": 面积数值, "units": "目标单位"} - 示例: '{"value": 0.2471, "units": "acres"}'

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

Example: >>> import asyncio >>> result = asyncio.run(convertArea(1000.0, 'meters', 'acres')) >>> print(result) '{"value": 0.2471, "units": "acres"}'

Notes: - 支持多种面积单位之间的转换 - 输入和输出单位必须是有效的单位标识符 - 转换基于标准单位换算系数 - 依赖于 Turf.js 库和 Node.js 环境

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYes
original_unitYes
final_unitYes
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 by disclosing key behaviors: it specifies the return format as JSON string, mentions exception conditions (JavaScript execution failure, timeout, input format errors), and notes dependencies on Turf.js and Node.js environment. However, it doesn't mention performance characteristics like rate limits or whether the operation is stateless.

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 parameter documentation could be more concise, but overall it's appropriately sized for a tool with 3 parameters and no annotations.

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, 3 parameters with no schema descriptions, no annotations, and no output schema, the description provides complete context. It covers purpose, parameters, return format, error conditions, examples, and implementation dependencies, leaving no significant gaps for agent understanding.

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 including types, descriptions, valid values with enums, and examples for all three parameters. It adds substantial meaning beyond the bare schema, making parameter usage clear and unambiguous.

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 as converting area values between units, with specific verb ('转换' meaning convert) and resource ('面积单位' meaning area units). It distinguishes itself from sibling tools like unit_conversion_convertLength by focusing specifically on area conversion, not length or other unit types.

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 context through parameter documentation and notes about valid unit identifiers, but doesn't explicitly state when to use this tool versus alternatives. It mentions sibling tools like unit_conversion_convertLength exist but provides no comparative guidance on choosing between area and length conversion tools.

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