Calcgrid

Search calculators

search_calculators

Read-onlyIdempotent

Use this when a user needs a deterministic calculation but none of the dedicated tools clearly matches and the calculator_id is unknown. Search 538 calculators from the complete task in English or Chinese, then call run_calculator with the top matching calculator_id and returned input_hints. Do not use this for trivial arithmetic, live data, writing tasks, or when a dedicated typed tool already matches. This tool only discovers; it does not calculate.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	Yes	The complete user task, including known values and units; for example 'compound interest on 15000 at 4.8% monthly for 12 years'.
`category`	No	Optional category id to restrict results.

Output Schema

TableJSON 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 / query / description

Previous value: -"Free-text query, e.g. 'compound interest' or 'body fat'."New value: +"The complete user task, including known values and units; for example 'compound interest on 15000 at 4.8% monthly for 12 years'."

addedInput schema / properties / query / examples

Added value: +[
+  "compound interest on 15000 at 4.8% monthly for 12 years"
+]

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

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds meaningful context beyond that: the tool only discovers and does not calculate, it searches 538 calculators in English or Chinese, and it returns input_hints to pass to run_calculator. No contradiction with annotations.

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 no wasted words. The usage condition is front-loaded, followed by behavior, exclusions, and a clarifying final sentence. 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?

Given the rich annotations, an output schema, and simple parameter set, the description fully covers what an agent needs: when to call, what it does, what it doesn't do, and the recommended next step. Nothing essential 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 coverage is 67%, with query and category already described. The description reinforces that query should be the complete user task and adds the English/Chinese language detail, but does not meaningfully elaborate on limit or category beyond the schema. Baseline 3 is appropriate since the schema carries most parameter meaning.

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 uses a specific verb ('Search'), names the resource ('538 calculators'), and clearly states the tool's scope ('This tool only discovers; it does not calculate'). It distinguishes itself from dedicated typed tools and run_calculator, so an agent can tell exactly what this tool is for.

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?

It explicitly states when to use ('when a user needs a deterministic calculation but none of the dedicated tools clearly matches and the calculator_id is unknown'), when not to use ('trivial arithmetic, live data, writing tasks, or when a dedicated typed tool already matches'), and names the follow-up action ('call run_calculator'). This is exemplary routing guidance.

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?