Skip to main content
Glama

CalcBright Calculators

Get a calculator's inputs

get_calculator_inputs
Read-onlyIdempotent

The JSON schema of one calculator's inputs (names, types, allowed values, defaults). Call before calculate when you are unsure of the input names.

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

Input Schema

NameRequiredDescriptionDefault
calculatorYesCalculator id from find_calculator, e.g. "uae-gratuity-calculator"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is covered. The description adds the useful data-contract detail (it returns names, types, allowed values, defaults) and the sequencing constraint relative to calculate, but it says nothing about failure behavior for unknown calculator ids or the size/shape of the response beyond the field list.

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 short sentences, zero filler, with the return contract front-loaded and the invocation guidance immediately after. Nothing redundant or padded.

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 by listing the four schema facets returned. Minor gaps remain — required-field information and error behavior on an invalid calculator id — but for a one-parameter lookup tool this is close to sufficient.

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% and the single parameter entry already states 'Calculator id from find_calculator' with a concrete example. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 names a specific resource (one calculator's input JSON schema) and enumerates what it contains — names, types, allowed values, defaults. It is clearly distinct from a calculation tool, though it differentiates from find_calculator only implicitly by referencing the calculator id usage rather than contrasting the two tools.

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?

It gives an explicit precondition for calling: use this before calculate when unsure of input names. The conditional 'when you are unsure' implicitly tells the agent to skip it when already confident, but no when-not case or named alternative is spelled out.

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