Scientific Calculator

calculator_scientific

Read-only

Use this tool to evaluate a scientific math expression with functions like sin, cos, sqrt, log, exp, and constants pi/e. Angles inside expressions use radians.

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": {
      "expression": "<expression>"
    },
    "name": "calculator_scientific"
  }
}

Input Schema

Name	Required	Description	Default
`expression`	Yes	Scientific expression to evaluate (e.g. 'sqrt(25)+pow(2,3)').

Output Schema

Name	Required	Description	Default
`output`	Yes
`result`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot express: angles are interpreted in radians, which directly affects correctness of results. It stops short of covering error behavior for malformed expressions or whether degrees are ever accepted.

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, no filler, with the core action stated first and the critical radians constraint immediately after. Nothing could be removed without losing semantic content.

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?

An output schema exists, so return values needn't be explained, and a one-required-parameter tool is low complexity. The description covers supported functions, constants, and unit conventions; only edge-case behavior (malformed input handling, whether degrees are accepted) is left unstated.

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 description coverage is 100% and the single parameter already carries examples, so the baseline is 3. The description earns above baseline by constraining expression syntax — naming the available functions and constants and fixing the angular unit to radians, which the schema's examples do not make explicit.

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?

States a specific verb and resource ("evaluate a scientific math expression") and enumerates supported functions and constants, so the agent knows exactly what class of input belongs here. It does not, however, differentiate itself from adjacent siblings such as calculator_basic, calculator_trigonometry, or calculator_logarithm.

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 opening "Use this tool to evaluate a scientific math expression" cues intended usage, but there is no explicit when-to-use versus when-not guidance and no named alternative for simpler arithmetic or single-function calls. Usage must be inferred from the function list.

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

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.