CalculatorLib

search_calculators

Read-onlyIdempotent

Search CalculatorLib by keyword in any of its 12 languages — payroll, tax and social-insurance calculators for Asian markets (year-correct, legal editions cited where available) and about 8,000 general calculators. Returns the best matches (name, title, and a ready-to-use input schema) ranked by relevance and popularity. Call this FIRST, then call run_calculator with the chosen name. Example queries: "Vietnam personal income tax", "lương gross sang net", "mortgage monthly payment", "body mass index".

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": {
      "query": "<query>"
    },
    "name": "search_calculators"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Optional language to search in and to return titles and labels in: en, es, vi, hi, ja, ko, tr, ar, ru, fr, zh, tw, pt, de (zh = Simplified, tw = Traditional Chinese; zh-CN / zh-TW / vi-VN style tags are accepted). Default: auto-detected from the query, so titles may come back in the query's language (e.g. vi, es, fr, ja) rather than English; pass lang (e.g. "en") to fix the language.
`limit`	No	Max results to return (default 8, max 25).
`query`	Yes	Keywords describing the calculation you need.

Output Schema

Name	Required	Description	Default
`count`	Yes
`query`	No
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so safety is covered; the description still adds real context: results are ranked by relevance and popularity, each carries a ready-to-use input schema, and editions are year-correct with legal citations where available. It does not mention pagination/truncation beyond the limit parameter or what happens on zero matches.

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?

Well front-loaded: purpose, corpus scope, return shape, next step, then examples — every sentence does work and the workflow instruction is not buried. The "12 languages" claim conflicts with the 14 codes enumerated in the schema, a small but avoidable inaccuracy.

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?

An output schema exists, so return values need minimal explanation, and the description still sketches the result shape and the follow-up call, which is more than enough for a 3-parameter search tool. The only real gap is the language-count mismatch and no guidance on empty result sets.

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 baseline is 3. The description does add useful query-shaping guidance through four example queries spanning English, Vietnamese, and different domains, but says nothing additional about lang or limit and even miscounts the languages ("12" vs the 14 codes in 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?

States a specific verb and resource ("Search CalculatorLib by keyword") and immediately scopes the corpus: payroll/tax/social-insurance calculators for Asian markets plus ~8,000 general calculators. An agent can tell it apart from run_calculator, convert_units, and solve_math without opening any schema.

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?

"Call this FIRST, then call run_calculator with the chosen name" gives an explicit ordering and names the downstream tool, which is strong routing guidance. It never states when *not* to use it (e.g. vs get_calculator_schema or solve_math for non-calculator math), so the alternative space is only partly covered.

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

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