TrueCalci

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

Name	Required	Description
`area`	Yes	Area to convert, in from_unit. Must be greater than 0.
`state`	No	Indian 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_unit`	No	Unit to convert into. If omitted, the area is returned in every standard unit.
`from_unit`	Yes	Unit of area. Regional units (bigha, biswa, katha ...) need state.
`as_of_date`	Yes	Statutory rule reference date (YYYY-MM-DD).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trace`	No
`status`	No
`to_unit`	No
`from_unit`	No
`as_of_date`	No
`disclaimer`	No
`input_area`	No
`rule_ids_used`	No
`state_applied`	No
`sqft_factor_to`	No
`converted_value`	No
`sqft_factor_from`	No
`standard_breakdown`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / to_unit / description

Previous value: -"Unit to convert into."New value: +"Unit to convert into. If omitted, the area is returned in every standard unit."

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "as_of_date": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "converted_value": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "from_unit": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "input_area": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "rule_ids_used": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "sqft_factor_from": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "sqft_factor_to": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "standard_breakdown": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "state_applied": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "to_unit": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "trace": {
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026

changedInput schema / required

Previous value: -[
-  "area",
-  "from_unit"
-]New value: +[
+  "area",
+  "from_unit",
+  "as_of_date"
+]

Changed8 schema fields changedSep 26, 2026

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"
+]

AddedSep 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds critical context beyond annotations: deterministic conversion, refusal rather than guessing when state is missing for regional units, and the exact return composition (target value, square-foot baseline, 7-unit breakdown). This is rich behavioral disclosure.

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 front-loaded with purpose and then organized into Behavior and Usage Guidelines sections. It is somewhat long, especially the state list, but every part is relevant and well-structured. It avoids redundancy and keeps the core usage rule easy to find.

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, the description covers the legal context, conditional state requirement, universal-vs-regional distinction, and return shape. An output schema exists, so return values need not be fully explained, but the description still summarizes them helpfully. Nothing an agent needs to call the tool correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains area, state, to_unit, from_unit, and as_of_date. The description reinforces that state is required for regionally ambiguous units and that to_unit omission returns all standard units, but these points are already present in the schema. It adds little new syntactic or semantic detail beyond the schema.

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 states a specific verb and resource: 'Convert Indian regional and universal land measurement units.' It distinguishes regional from universal units and names the governing legal framework, making the tool's scope immediately clear. Sibling tools are all finance/tax calculators, so no further differentiation is needed.

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 gives explicit usage guidance: 'Specify state when converting traditional units (e.g. bigha or katha) to avoid ambiguous multi-fold variance.' It also implicitly frames usage under the Legal Metrology Act and State Land Revenue Codes. However, it does not state when not to use the tool or name alternatives, which is reasonable given the lack of sibling overlap.

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

All TrueCalci tools Inspect

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

Need Help?