Skip to main content
Glama

Run calculator

run_calculator
Read-only

Runs a calculator and returns its exact results, the step-by-step working where available, and a url that opens the calculator with these inputs. Inputs left out use the defaults from get_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": {
      "slug": "<slug>"
    },
    "name": "run_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
inputsNoInput values by key, e.g. {"principal": 20000, "annualRate": 7}. Select inputs take one of the listed option values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the description's real contribution is the return-content disclosure: exact results, step-by-step working 'where available,' and a shareable URL. It also reveals partial-input behavior via defaults. The hedge 'where available' is useful honesty; missing is any note on invalid slug or unsupported input handling.

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?

A single sentence with the action first and the three return artifacts enumerated after it. No filler, no repetition of the title, and the most decision-relevant fact (the returned URL) is stated plainly.

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 correctly takes on the burden of describing return values and does so thoroughly, and it explains defaulting behavior for a nested-object parameter. The remaining gap is provenance of the required slug, which an agent must infer from sibling names.

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 50%: the 'inputs' object carries its own description with an example and a note that select inputs take listed option values, while 'slug' is undocumented in both schema and description. The description adds genuine semantics for 'inputs' by explaining that omitted keys fall back to get_calculator defaults, but leaves the required slug entirely unexplained.

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 verb and resource ('Runs a calculator') and goes on to enumerate what it produces: exact results, step-by-step working, and a URL that reopens the calculator with these inputs. That output inventory separates it from the metadata siblings (get_calculator, list_calculators, search_calculators), though it never states the contrast explicitly.

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?

Usage is only implied. The clause 'Inputs left out use the defaults from get_calculator' hints that get_calculator is a companion for defaults, but there is no statement of when to call this tool versus those siblings, and no guidance on where the required slug comes from (presumably list_calculators or search_calculators).

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