Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_scientific_calculator

Read-onlyIdempotent

Evaluate scientific math expressions with trigonometry, logarithms, powers, and constants. Supports degrees or radians for trig functions.

Instructions

Scientific Calculator Expression Evaluator. Evaluate a single scientific math expression and return its numeric value, with support for trigonometry (sin, cos, tan, asin, acos, atan, atan2), logarithms (ln, log base 10, log2), exponent and power, square and cube root, abs, floor, ceil, round, factorial (n! or factorial), modulo (% or mod), the constants pi and e, and parentheses for grouping. The angleMode option selects whether trig functions read their argument in radians (default) or degrees. Uses a hand-rolled shunting-yard parser (no JavaScript eval and no dynamic code execution), so only the documented operators and functions run. Use this for general numeric expressions; use math_quadratic_solver to solve ax^2 + bx + c for roots, or math_statistics_calculator for descriptive statistics over a dataset. Runs locally on the expression you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests per minute for anonymous callers). On success returns the original ex

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expressionYesMath expression to evaluate (max 1000 characters). Supports plus, minus, times, divide, modulo, power operators, the mod keyword, parentheses, factorial via bang or factorial(), functions (sin cos tan asin acos atan atan2 ln log log2 exp sqrt cbrt abs floor ceil round max min), constants pi and e, and scientific notation such as 1.5e10. Must not be blank.
angleModeNoAngle unit for trig and inverse-trig functions: rad treats arguments as radians, deg as degrees. Aliases radians and degrees are accepted.rad

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the expression evaluated successfully.
resultNoThe evaluation payload.
Behavior5/5

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

Beyond annotations, the description discloses critical behavioral traits: uses a hand-rolled shunting-yard parser (no eval), runs locally as read-only and non-destructive, contacts no external service, and is rate-limited at 60 requests/minute. This transparency far exceeds the minimal annotation hints.

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?

The description is front-loaded with the core purpose and well-structured, covering operators, usage guidance, and safety. However, it is somewhat verbose and includes a truncated sentence at the end, slightly reducing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown but indicated), the description does not need full return details. However, the description is truncated mid-sentence ('On success returns the original ex'), which is a clear gap. Otherwise, it covers supported operations, error handling implied, and limitations.

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?

Both parameters have full schema descriptions (100% coverage), but the description adds value by elaborating on angleMode aliases and clarifying the expression length limit (1000 characters). This enhances understanding beyond 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?

The description clearly states the tool evaluates a single scientific math expression and returns its numeric value. It explicitly lists supported functions and operators, and distinguishes itself from sibling tools like math_quadratic_solver and math_statistics_calculator by stating when to use each.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool (general numeric expressions) and when to use alternatives (quadratic solver, statistics calculator). It also mentions rate limits and safety, helping the agent decide correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server