Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

area_convert

Convert area units: m2, km2, hectares, acres and square feet. Pure CPU, instant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>"
    },
    "name": "area_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit
fromNoSource unit
valueYesValue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Source unit",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Target unit",
+  "type": "string"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Value",
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "value"
+]
  4. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. 'Pure CPU, instant' usefully signals no external dependencies and fast execution, but it omits precision/rounding behavior and what happens with invalid unit strings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste. The conversion purpose and supported units are front-loaded, and the performance note is relevant behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter tool with no output schema and no annotations, the description is adequate but incomplete. It does not clarify default behavior when optional 'from'/'to' are omitted, precision or rounding rules, or the return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful parameter context by listing accepted area units, which the schema does not enumerate, though it does not explain the optional nature or defaults for 'from' and 'to'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Convert area units' and lists the supported area units. It clearly distinguishes this from non-area converters, though it does not explicitly name nearby generic siblings such as unit_convert or convert_units.

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?

Usage is implied by the listed area units, but there is no explicit guidance on when to use this tool versus generic conversion siblings or when not to use it. No prerequisites or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GadgetHumans API Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources