Skip to main content
Glama

TrueCalci

by com.truecalci
OverviewDiscussionsAdmin

Gold valuation

gold
Read-onlyIdempotent

Calculate Gold and Silver commodity valuation, hallmarking purity adjustments (24K, 22K, 18K, 14K), statutory GST (3%), making charges, and Indian regional unit conversions (Tola, Sovereign, Sovereign/Pavan, Grams, Troy Ounces).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_of_dateYesCivil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.
purity_karatYesPurity in Karats (24K pure, 22K standard jewellery 916, 18K 750, 14K 585). Required - the engine never assumes a hallmark.
weight_gramsYesWeight of gold in grams.
rate_per_gram_24kYesCurrent market price of 24K gold per gram in INR (₹), as a string with exactly 2 decimal places (money is never a float).
making_charges_percentNoMaking charges as percentage of pure metal value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / as_of_date
      Added value: +{
+  "description": "Civil date YYYY-MM-DD. Selects the rule pack in force on that date. Required: the engine will not assume a date.",
+  "example": "2026-09-26",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "weight_grams",
-  "rate_per_gram_24k",
-  "purity_karat"
-]New value: +[
+  "weight_grams",
+  "rate_per_gram_24k",
+  "purity_karat",
+  "as_of_date"
+]
  2. Changed7 schema fields changed
    • removedInput schema / properties / purity_karat / default
      Removed value: -22
    • changedInput schema / properties / purity_karat / description
      Previous value: -"Purity in Karats (24K pure, 22K standard jewellery 916, 18K 750, 14K 585)."New value: +"Purity in Karats (24K pure, 22K standard jewellery 916, 18K 750, 14K 585). Required - the engine never assumes a hallmark."
    • changedInput schema / properties / rate_per_gram_24k / description
      Previous value: -"Current market price of 24K gold per gram in INR (₹)."New value: +"Current market price of 24K gold per gram in INR (₹), as a string with exactly 2 decimal places (money is never a float)."
    • addedInput schema / properties / rate_per_gram_24k / example
      Added value: +"7500.00"
    • addedInput schema / properties / rate_per_gram_24k / pattern
      Added value: +"^\\d+\\.\\d{2}$"
    • changedInput schema / properties / rate_per_gram_24k / type
      Previous value: -"number"New value: +"string"
    • changedInput schema / required
      Previous value: -[
-  "weight_grams",
-  "rate_per_gram_24k"
-]New value: +[
+  "weight_grams",
+  "rate_per_gram_24k",
+  "purity_karat"
+]
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior; the description adds the exact calculation components: hallmark adjustments (24K/22K/18K/14K), statutory GST 3%, making charges, and regional unit conversions. This goes beyond annotations but stops short of describing output shape or the silver-input discrepancy.

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?

A single dense sentence that front-loads the main purpose and packs the feature list without fluff. The comma-separated list is efficient, though it reads slightly like a feature dump rather than structured guidance.

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?

With rich schema descriptions and annotations, the agent has the parameter and safety context to invoke the tool. The description's calculation scope fills the behavioral gap, but the unbacked 'Silver' claim and absence of any output-format hint leave minor gaps.

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 covers 100% of parameters, including examples, patterns, enums, and defaults, so the baseline is 3. The description adds domain context (GST 3%, making charges, conversions) but no parameter-specific detail beyond what the schema already provides.

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 opens with 'Calculate Gold and Silver commodity valuation' and enumerates specific sub-computations (purity, GST, making charges, conversions), which is a clear verb+resource statement. It distinguishes this tool from the tax and investment siblings by subject matter, though no sibling is named. The mention of 'Silver' is unsupported by the input schema, which only includes gold-specific parameters, slightly diluting clarity.

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 use for gold valuation calculations, and the sibling list contains no other gold-specific valuation tool, so the agent can infer applicability. However, there is no explicit when-to-use or when-not-to-use guidance, no alternative tool references, and the unsupported 'Silver' claim muddies the boundaries.

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