Skip to main content
Glama

Area unit converter

bpj_units_area
Read-onlyIdempotent

Convert drawing and land areas. Enter one of m2, cm2, mm2, km2, ft2, in2, ha, acre to return the equivalent value in every listed unit.

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>",
      "unit": "<unit>"
    },
    "name": "bpj_units_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds genuine value by disclosing the output shape — a value in every listed unit rather than a single converted figure — since there is no output schema. It says nothing about rounding/precision or whether the unit token is case-sensitive.

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 sentences, zero filler, with the purpose front-loaded and the accepted inputs plus return behavior following immediately. Nothing is repeated from the title or annotations.

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

Completeness4/5

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

For a two-parameter, side-effect-free converter with no output schema, the definition covers purpose, valid unit tokens, and return behavior. Minor gaps (precision of returned values, case sensitivity of unit strings) are the only things an agent might still need.

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 0% with no enums, so the description carries the burden, and it does: it enumerates the eight accepted unit tokens (m2, cm2, mm2, km2, ft2, in2, ha, acre) and clarifies that exactly one unit is supplied while all units are returned. The numeric range constraints for 'value' are left to the schema.

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?

States a specific verb (Convert) and a clearly bounded resource (drawing and land areas), and the unit list pins down that this is the area converter among the many bpj_units_* siblings. It doesn't name an alternative explicitly, but the domain word 'area' makes the separation obvious.

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 tells the agent what input to supply ('Enter one of ...') and what comes back, which implies when the tool applies. It offers no explicit when-to-use vs when-not guidance or contrast with sibling converters such as bpj_units_length.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.