Skip to main content
Glama

SmartTools

by io.github.9thShini

Scientific calculator

scientific_calculator

Evaluate a math expression with correct order of operations: + - * / % ^, parentheses, and functions (sqrt, sin, cos, tan, ln, log, exp, min, max, factorial via !). Constants pi, e. Angles in radians. Runs on smart-tools.xyz.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoLanguage for the source_url link (default en)
expressionYesMath expression, e.g. "2+3*sqrt(16)" or "sin(pi/6)". Operators + - * / % ^ (% is remainder, ^ is power), functions sqrt/cbrt/abs/ln/log/log2/exp/sin/cos/tan/asin/acos/atan/sinh/cosh/tanh/round/floor/ceil/sign/deg/rad/min/max/mod/pow/hypot, factorial via trailing !, constants pi/e/tau. Angles in radians.

TDQS

A3.7/5.0
Behavior3/5

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

The description discloses key behaviors like order of operations, supported functions, constants, and radians. However, it doesn't mention error handling, precision, or return format. Without annotations, these details would be helpful but the core behavior is still reasonably transparent.

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 concise and front-loaded with the core purpose. The final sentence 'Runs on smart-tools.xyz' is extraneous and not directly useful for tool selection, but the overall length is appropriate and information-dense.

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?

For a calculator tool, the description covers supported operations, angle mode, and constants. No output schema exists, but the return value is implied (numeric result). It lacks explicit error-recovery or precision details, but these are less critical for a calculator. Overall it is sufficiently complete.

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%, with detailed parameter documentation. The tool description reiterates some functions but adds contextual details like angle mode and order of operations. However, the schema already provides most of this, so the description adds limited incremental value.

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 math expressions with correct order of operations, listing operators, functions, and constants. This distinguishes it from sibling calculators by focusing on general expression evaluation rather than specific domain calculations.

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 description implies when to use the tool (for evaluating math expressions) but provides no explicit alternatives or exclusions. It doesn't say 'use this for general math, not for unit conversion' or similar. Usage is clear but not contrasted with siblings.

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

All SmartTools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation3/5

Most tools are clearly distinct, but there are notable overlaps. 'hash_generator' and 'file_hash' effectively do the same thing (SHA hashing of text), and several CSV/TSV converters (csv_to_json, csv_to_sql, table_to_csv, markdown_table) have similar input handling, though outputs differ. The sheer number of converters is clear, but these near-duplicates create some ambiguity.

Naming Consistency4/5

Names follow a generally consistent pattern: lowercase with underscores, often ending in 'converter', 'calculator', or 'generator'. A few names like 'base64', 'lorem_ipsum', and 'transliteration' deviate from the suffix pattern, but the naming style is uniform and predictable overall.

Tool Count2/5

With 73 tools, this server is far over the typical well-scoped range. While the broad utility-toolkit purpose might justify a larger set, 73 is unwieldy and pushes well into 'too many' territory, making it harder for an agent to select the right tool efficiently.

Completeness4/5

The server covers a remarkably wide range of common utilities: unit conversions, calculators, text transformations, development helpers (JSON, regex, JWT, subnet), and generators. Minor gaps exist (e.g., currency converter, time zone converter), but for a general-purpose toolkit, it is largely comprehensive.

Resources