calculator-mcp-server
Server Details
Calculator MCP server — evaluate, simplify, and differentiate math expressions.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/calculator-mcp-server
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
1 toolcalculateCalculateARead-onlyIdempotentInspect
Evaluate math expressions, simplify algebraic expressions, or compute symbolic derivatives. Supports arithmetic, trigonometry, statistics, matrices, complex numbers, units, and combinatorics. Powered by math.js — use calculator://help for the full function reference.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Variable assignments for the expression. Example: { "x": 5, "y": 3 } makes "x + y" evaluate to 8. | |
| variable | No | Variable to differentiate with respect to. Required when operation is "derivative". Example: "x". | |
| operation | No | Operation to perform. "evaluate" computes a numeric result (default). "simplify" reduces an algebraic expression symbolically (e.g., "2x + 3x" -> "5 * x"). Supports algebraic and trigonometric identities. "derivative" computes the symbolic derivative (requires variable parameter). | evaluate |
| precision | No | Significant digits (1–16) for numeric results. Omit for full precision. Ignored for symbolic operations (simplify, derivative). | |
| expression | Yes | Mathematical expression to evaluate. Supports standard notation: arithmetic (+, -, *, /, ^, %), functions (sin, cos, sqrt, log, abs, round, etc.), constants (pi, e, phi, i), matrices ([1, 2; 3, 4]), units (5 kg to lbs), and variables (when scope is provided). |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | The computed result as a string. |
| expression | Yes | The original expression as received. |
| resultType | Yes | Type of result as reported by math.js: number, BigNumber, Complex, DenseMatrix, Unit, string, boolean. Symbolic operations return "string". |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnly, idempotent, and closed-world properties. The description adds valuable context beyond these flags by identifying the underlying engine (math.js) and providing a help reference (calculator://help) for function syntax. It also enumerates specific capability domains (units, combinatorics, complex numbers) that inform the agent of the tool's reach.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences total, front-loaded with core functionality. Every sentence earns its place: sentence 1 states purpose, sentence 2 lists capabilities, sentence 3 cites documentation source. No redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the existence of an output schema and 100% input schema coverage, the description appropriately delegates parameter details to the schema. It successfully signals the tool's extensive capabilities (via the domain list and math.js reference) and points to external help for exhaustive function documentation, which is the correct approach for a calculator with broad function support.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the structured data fully documents all five parameters including the operation modes and scope object. The description mentions the three operations in the opening sentence but does not add semantic details (e.g., syntax examples, interplay between scope and expression) beyond what the schema already provides. Baseline 3 is appropriate given the comprehensive schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with specific verbs (Evaluate, simplify, compute) and resources (math expressions, algebraic expressions, symbolic derivatives). It further clarifies scope by listing supported domains (arithmetic, trigonometry, statistics, matrices, etc.). With no siblings present, this fully establishes the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description distinguishes three distinct use cases (evaluation, simplification, derivatives) that map to the operation enum. It references 'calculator://help' for detailed function syntax, providing clear context for when to use the tool (mathematical computation). No explicit 'when-not' guidance is present, but there are no siblings to contrast against.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!