Calcgrid

Get calculator schema

get_calculator_schema

Read-onlyIdempotent

Use this only after search_calculators when its input_hints do not resolve a range, enum or optional-field question. Return the full input/output schema, formula, sources, examples and limitations for one calculator. Do not call it when the search result already supplies enough input detail; call run_calculator instead. This tool only describes and does not calculate.

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": {
      "calculator_id": "<calculator_id>"
    },
    "name": "get_calculator_schema"
  }
}

Input Schema

Name	Required	Description	Default
`calculator_id`	Yes	Exact calculator_id returned by search_calculators; for example 'bmi' or 'compound-interest'.

Output Schema

Name	Required	Description	Default
`links`	No
`result`	Yes
`request`	No
`success`	Yes
`timestamp`	Yes
`next_actions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 25, 2026

changedInput schema / properties / calculator_id / description

Previous value: -"Calculator id from search_calculators, e.g. 'bmi'."New value: +"Exact calculator_id returned by search_calculators; for example 'bmi' or 'compound-interest'."

addedInput schema / properties / calculator_id / examples
```
Added value: +[
+  "compound-interest"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Read-only catalogue or schema result used to select a calculation tool.",
+  "properties": {
+    "links": {
+      "type": "object"
+    },
+    "next_actions": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "request": {
+      "type": "object"
+    },
+    "result": {
+      "type": "object"
+    },
+    "success": {
+      "const": true,
+      "type": "boolean"
+    },
+    "timestamp": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "result",
+    "timestamp"
+  ],
+  "type": "object"
+}

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds the explicit statement 'This tool only describes and does not calculate.' This prevents misinterpretation even without annotations. Since annotations cover safety, the description adds a small but useful behavioral clarification, earning a 4.

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?

Three sentences with zero filler. The primary usage condition is front-loaded, alternatives are named in the second sentence, and a final clarifying disambiguation closes it. Every sentence earns its place.

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?

With a simple one-parameter input, full schema coverage, and annotations covering safety/idempotence, the description is complete. It explains when to use, what it returns (schema, formula, sources, etc.), and that it does not calculate. Nothing essential is missing for an agent to call it correctly.

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?

The schema has 100% coverage for calculator_id, but the description reinforces that the ID comes from search_calculators, adding context beyond the schema's example list. It also clarifies the ID is exact, which prevents guesswork. This goes beyond the schema baseline of 3, so a 4 is justified.

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 ('get') and resource ('calculator schema'), and clearly distinguishes itself from siblings by mentioning when not to use it (when search results suffice) and when to use run_calculator instead. It is not a tautology and instantly conveys the tool's role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('only after search_calculators when input_hints...'), when not to use it ('do not call when search result already supplies enough'), and names the alternative (run_calculator). This is direct usage guidance with clear conditions and exclusions.

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

All Calcgrid 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?