Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

Land area unit conversion

land_units
Read-onlyIdempotent

Convert Indian regional and universal land measurement units under the Legal Metrology Act, 2009 and State Land Revenue Codes (UP, Punjab, Haryana, West Bengal, Gujarat, Bihar, Assam, HP, MP, Rajasthan).

Behavior: Deterministic, idempotent conversion that requires the state for regional units (Bigha, Katha, Biswa, etc.), because their size differs by state, and refuses rather than guesses. Universal units (sqft, sqm, gaj/sqyd, acre, hectare, guntha, cent, ground, ankanam) resolve nationally. Returns target converted value, square foot baseline, and complete 7-unit standard breakdown.

Usage Guidelines: Specify 'state' when converting traditional units (e.g. 'bigha' or 'katha') to avoid ambiguous multi-fold variance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaYesArea to convert, in from_unit. Must be greater than 0.
stateNoIndian state name or 2-letter code (e.g. 'UP', 'WEST_BENGAL', 'GUJARAT', 'PUNJAB', 'HARYANA', 'BIHAR', 'ASSAM', 'HP', 'MP', 'RAJASTHAN'). Required for regionally ambiguous units.
to_unitNoUnit to convert into.
from_unitYesUnit of area. Regional units (bigha, biswa, katha ...) need state.
as_of_dateYesStatutory rule reference date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "area",
-  "from_unit"
-]New value: +[
+  "area",
+  "from_unit",
+  "as_of_date"
+]
  2. Changed8 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Numeric area string to convert (e.g. '1.0', '3.875', '100'). Must be positive."New value: +"Area to convert, in from_unit. Must be greater than 0."
    • addedInput schema / properties / area / example
      Added value: +2.5
    • addedInput schema / properties / area / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / area / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / properties / from_unit / description
      Previous value: -"Source land area unit (e.g. 'bigha', 'acre', 'sqft', 'sqm', 'guntha', 'katha', 'marla', 'kanal', 'cent')."New value: +"Unit of area. Regional units (bigha, biswa, katha ...) need state."
    • addedInput schema / properties / from_unit / enum
      Added value: +[
+  "sqft",
+  "sqm",
+  "gaj",
+  "sqyd",
+  "acre",
+  "hectare",
+  "guntha",
+  "cent",
+  "ground",
+  "ankanam",
+  "bigha",
+  "bigha_pucca",
+  "bigha_kaccha",
+  "biswa",
+  "katha"
+]
    • changedInput schema / properties / to_unit / description
      Previous value: -"Optional specific target unit (e.g. 'sqft', 'acre', 'guntha', 'sqm', 'biswa'). If omitted, returns full standard breakdown."New value: +"Unit to convert into."
    • addedInput schema / properties / to_unit / enum
      Added value: +[
+  "sqft",
+  "sqm",
+  "gaj",
+  "sqyd",
+  "acre",
+  "hectare",
+  "guntha",
+  "cent",
+  "ground",
+  "ankanam"
+]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds valuable behavioral context: it is deterministic, refuses rather than guesses when state is missing, and explains that regional units have state-dependent sizes. It also discloses the return structure (target value, square foot baseline, and 7-unit standard breakdown), which annotations do not provide.

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-organized into labeled sections with the core action front-loaded. It is concise overall, though the requirement to specify state for regional units is stated in both the Behavior and Usage Guidelines sections, creating minor redundancy.

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?

The description covers the central complexity of state-dependent regional units and the refusal behavior, and explains return values despite no output schema. However, it offers little context about the required 'as_of_date' parameter beyond the schema's terse 'statutory rule reference date' text, so an agent unsure how to choose that date gets limited guidance.

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 semantics by explaining why 'state' is conditionally required and that universal units resolve nationally, which helps the agent understand the relationship between from_unit and state. This goes just beyond the schema without fully documenting every conditional combination.

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 opens with a specific verb and resource: 'Convert Indian regional and universal land measurement units', and further scopes it by legal framework and states. This clearly differentiates it from the finance/tax-focused sibling tools and leaves no doubt about what the tool does.

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?

There is an explicit 'Usage Guidelines' section instructing to specify 'state' for traditional units like bigha or katha to avoid ambiguous multi-fold variance. It gives clear context but does not name alternative tools or enumerate when not to use this tool; however, the sibling set is unrelated enough that this is a minor gap.

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

All TrueCalci 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