TrueCalci

Statutory rule pack status

pack_status

Read-onlyIdempotent

Lists the official rate tables each calculator uses (free, no credits). Shows the active government rate tables (AY 2025-26, IRS Rev. Proc., HMRC, etc.), hash checksums, and legal enactment citations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`engineId`	No	Optional engine ID (e.g. 'tds', 'tcs', 'gst_regular', 'advance_tax', 'vat_sales_tax', 'tax_in') to query specific statutory pack metadata.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`class`	No
`packs`	No
`credits`	No
`service`	No
`timestamp`	No
`total_engines`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "class": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "credits": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "packs": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "service": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "total_engines": {
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 11, 2026

TDQS

A3.8/5.0

Behavior4/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 valuable context beyond that: it is free/no-credit and returns active rate tables, hash checksums, and legal citations, though it does not discuss pagination or output limits.

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 front-loaded sentences with no filler. The first states the core purpose and free status; the second details the returned content, and nothing is wasted.

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 annotations covering safety, schema covering the only parameter, and an output schema present, the description provides enough for correct invocation. It could be slightly stronger by clarifying when engineId should be omitted versus supplied, but overall it is complete for this metadata tool.

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?

The schema has 100% description coverage for the single optional engineId parameter, including examples and its purpose. The description itself adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 gives a specific verb and resource: it lists the official rate tables each calculator uses and shows active government rate tables, checksums, and legal citations. It is clearly distinguishable from the calculator siblings, though it does not explicitly name an alternative or sibling.

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?

It notes the tool is free with no credits, which is useful usage context, but does not state when to use this status tool versus the calculator tools or when it is unnecessary. The intended use is implied rather than explicit.

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?