Skip to main content
Glama

CalcBright Calculators

Run a calculator

calculate
Read-onlyIdempotent

Run any CalcBright calculator and get the exact result plus a link to the full worked calculation. Omitted inputs use the calculator's defaults.

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": "<calculator>"
    },
    "name": "calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoInput values by name (see get_calculator_inputs)
calculatorYesCalculator id, e.g. "vat-calculator"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=false), so the bar is lower. The description still adds real value by disclosing the return shape (result plus a link to the worked calculation) and the default-substitution behavior, though it says nothing about invalid calculator ids or error handling.

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?

Two tight sentences with the capability stated first and the defaults caveat second; nothing is filler. Slightly more structure, such as naming how to obtain a calculator id, would have earned a 5 without bloat.

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?

With no output schema, the description carries the return-value burden and does so adequately by naming the result and the worked-calculation link. It is nearly complete for a two-parameter, annotated read tool, with only the calculator-id discovery path and failure behavior left implicit.

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%, so the schema already documents both `calculator` and `inputs`, making the baseline 3 appropriate. The description slightly enriches the optional `inputs` parameter by explaining that omitted values fall back to calculator defaults, which the schema does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb and resource ('Run any CalcBright calculator') with the outcome ('exact result plus a link to the full worked calculation'), so the agent knows exactly what this tool produces. It does not distinguish itself from the sibling calculators it can run (vat_calculator, zakat_calculator, etc.), leaving the generic-vs-specific choice unaddressed.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance in the description. The only routing hint is indirect: the `inputs` schema field says 'see get_calculator_inputs', which implies a discovery flow but is buried in the schema rather than stated in the description.

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