Skip to main content
Glama

CalcBright Calculators

Find a calculator

find_calculator
Read-onlyIdempotent

Search CalcBright's 167 calculators (Gulf end of service, salary, GOSI, VAT, zakat, loans, mortgages, currency, dates, health, math) with a plain question in English, Arabic or Urdu. Returns the best matches with their ids.

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": "find_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the user wants to work out, e.g. "gratuity after 6 years in Dubai"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and closed-world, so safety is covered. The description adds genuine behavior beyond that: catalog size (167), the multilingual query surface, and that results are ranked 'best matches' keyed by id.

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 sentences, zero filler, with the capability and the return value front-loaded before the language qualification.

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?

No output schema exists, but the description states the shape of the return (best matches with ids), which is the key missing piece. It does not say what happens on no-match or how many results come back, a small gap for a one-parameter search 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?

Schema coverage is 100% with a single, well-exemplified query parameter, so the baseline is 3. The description adds only that the query may be in English, Arabic or Urdu and should be phrased as a plain question — helpful, but a modest increment over 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 (Search) and resource (167 calculators) and enumerates the covered domains, plus what comes back ('best matches with their ids'). It is clearly the discovery entry point among siblings that are each single-topic calculators, so an agent can tell it apart without opening a schema.

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?

The framing of a 'plain question in English, Arabic or Urdu' implies this is the tool to use when the user describes a need rather than naming a calculator, and the returned ids imply a follow-up call to a sibling. However, it never explicitly states when to use this instead of calling a specific calculator such as vat_calculator or calculate, nor any exclusion.

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