Skip to main content
Glama

Search calculators

search_calculators
Read-onlyIdempotent

Searches Calcupedia's 2,500+ calculators and unit converters by keyword (for example "mortgage", "bmi", "kg to lbs"). Returns matching calculators with their slug, category and page link; the top 3 also list their input keys, defaults and allowed values. Use it when the user wants a number worked out (a loan or mortgage payment, interest, savings, tax, salary, BMI, calories, a date or age, a percentage or a unit conversion) or asks for a calculator, then pass the slug to run_calculator.

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

NameRequiredDescriptionDefault
limitNoMaximum results, 1-20. Default 10.
queryYesKeywords for the calculator or conversion needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return shape: slug, category, page link, plus input keys/defaults/allowed values for the top 3 results. That 'top 3 only' enrichment detail is genuinely non-obvious and useful. It stops short of stating how ranking works or whether results are paginated beyond the limit cap.

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?

Front-loaded with the action and corpus, then the return shape, then the usage trigger. It is dense and mostly earns its length, though the long parenthetical use-case list runs a little heavy for a single sentence.

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?

There is no output schema, and the description compensates by describing exactly what comes back, including the top-3 enrichment fields. Combined with the chaining instruction to run_calculator, an agent has everything needed to call this and act on the result.

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?

Schema coverage is 100%, so baseline is 3, but the description adds keyword-style guidance with examples ('mortgage', 'bmi', 'kg to lbs') that clarify what a good query string looks like, which the schema does not. The limit parameter is left entirely to the schema, and the interaction between limit and the 'top 3' enrichment is unstated.

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 ('Searches Calcupedia's 2,500+ calculators and unit converters by keyword') and implicitly distinguishes itself from run_calculator by ending with a handoff ('pass the slug to run_calculator'). An agent can tell this is the discovery step, not the execution step.

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?

Gives an explicit trigger condition ('when the user wants a number worked out') with concrete examples (loan, interest, BMI, unit conversion, age) and names the follow-on alternative run_calculator with the parameter needed to use it. Nothing about routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources