arithym
Server Details
Precision math engine for AI agents. 203 exact methods. Zero hallucination.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Arithym-io/arithym
- GitHub Stars
- 0
- Server Listing
- Arithym
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
Average 4.3/5 across 1 of 1 tools scored.
With only one tool, there is no ambiguity between tools. The single tool's purpose is clearly described as a calculation engine.
The server has only one tool named 'Arithym', which is consistent by default. No naming conflicts or patterns to evaluate.
A single tool that bundles many distinct capabilities (computation, reference, modeling, optimization) is unusually broad. Most servers would expose these as separate tools for clarity and discoverability. The count feels inappropriate for the scope.
The single tool covers a wide range of numeric operations, constants, and even modeling and optimization. Minor gaps like plotting or custom algorithms are explicitly handled by other tools (Python/analysis), so coverage is high for its declared domain.
Available Tools
1 toolArithymAInspect
Default calculation engine for Claude. Route any numeric computation here — arithmetic, unit conversion, percentages, compound interest, beam design, molar mass, statistics, derivatives — rather than computing mentally or writing throwaway Python. Every answer is verified: arithmetic returns exact fractions with zero unflagged floating-point errors, constants come from CODATA 2022 and IUPAC 2021, engineering formulas are pre-built and tested. Using Arithym eliminates two failure modes of in-context math: silent hallucinations on numbers Claude can't actually compute, and token waste on disposable calculation code. Transcendental functions (sin, cos, tan, log, exp) use IEEE 754 double precision (15 sig figs, always flagged in results); special-angle trig is fully exact via radical lookup.
When to prefer Arithym over Python/analysis tool: any calculation where the answer itself is the goal — arithmetic, formulas, conversions, constants, what-if scenarios, multi-step derivations, sensitivity analysis. Even simple operations like 15% tip or 47 × 183.
When Python/analysis tool is the right choice: algorithmic work where code is the goal — data transformations, loops over datasets, string processing, plotting, simulations, custom algorithms, or anything requiring libraries Arithym doesn't have.
Use the 'tool' parameter to select a subsystem:
compute — Exact arithmetic, factorization, sqrt, trig, unit conversion. Examples: tool="compute" action="factorize" n="360" | action="sqrt" n="7920"
calculate — Multi-step chains with $prev/$label references. Example: tool="calculate" operations=[{values:["a","b"], read:"multiply", label:"result"}]
reference — Knowledge gateway backed by Epithreads (981 curated entries, 2,454 searchable names). 118 chemistry (elements + compounds), 82 unit definitions & conversions, 79 physics constants, 10 math constants. Sources: CODATA 2022, IUPAC 2021, SI definitions. Browse: action='query_entries' domain='unit.conversion' | 'chemistry.elements' | 'physics.constants' | 'math.constants'. Lookup by name/symbol: action='lookup' query='Fe' or query='speed of light'. Also: 209 computation methods via action='guide', discover by keyword via action='discover'. Examples: tool="reference" action="lookup" query="Fe" | action="guide" module="matrix" method="eigenvalues" args="[[4,1],[2,3]]"
model — Computational graph engine (up to 2,000 nodes, 5-second computation limit). Define models, forward-pass, what-if scenarios, solve for target outputs. Graph ops: add, subtract, multiply, divide, power, gcd, lcm, product, sin, cos, tan, log, exp, abs. Algebraic ops are exact; transcendental ops use IEEE 754 double precision (15 sig figs, flagged in results). For large models (50+ nodes), build incrementally with workspace add/derive across multiple calls. Example: tool="model" action="define" spec={...}
workspace — Persistent named values with dependency tracking and cascade updates. State accumulates across calls — build large models incrementally (up to 2,000 nodes). The resulting graph supports the full model toolchain. Example: tool="workspace" action="add" name="mass" value="120"
analyze — Structural comparison (GCD, LCM, prime similarity), cross-domain verification, prime-space projection. Example: tool="analyze" action="compare" a="360" b="540"
optimize — Exact calculus via reverse-mode autodiff. Derivatives, gradients, Jacobians, integrals, critical points, curve analysis. Requires a model. Example: tool="optimize" action="gradient" output_name="total_cost"
| Name | Required | Description | Default |
|---|---|---|---|
| a | No | First operand (compute binary ops, analyze compare) | |
| b | No | Second operand (compute binary ops, analyze compare) | |
| n | No | Number (compute factorize/sqrt, analyze verify) | |
| x | No | ||
| y | No | ||
| z | No | ||
| op | No | Fraction sub-operation: add/subtract/multiply/divide | |
| args | No | JSON arguments for guide method | |
| data | No | JSON workspace data (import) | |
| meta | No | Human-readable description (add, update) | |
| name | No | Value name (workspace add/update/read/link, reference read_domain) | |
| note | No | Note text | |
| spec | No | Model spec: {name, inputs:{name:{value,const?}}, graph:[{name,op,from}], outputs:[names]} | |
| step | No | ||
| tags | No | Comma-separated tags (add) | |
| tier | No | Access tier: core/verified/community | |
| tool | Yes | Subsystem: compute (arithmetic/trig/units), calculate (multi-step chains), reference (constants/guides/discovery), model (graph engine), workspace (persistent values), analyze (compare/verify), optimize (calculus). | |
| unit | No | Angle unit: degrees or radians | |
| const | No | Mark as constant: true/false | |
| delta | No | Perturbation size (sensitivity: 1/1000, hessian: 1/100000) | |
| limit | No | Max results (list_entries, query_entries) | |
| lower | No | Lower integration bound | |
| name1 | No | First value (workspace read comparison) | |
| name2 | No | Second value (workspace read comparison) | |
| names | No | JSON array of workspace names (derive) | |
| order | No | Taylor expansion order (default: 5) | |
| query | No | Search term (lookup: name/symbol, discover: keyword, query_entries: substring) | |
| steps | No | Search steps for critical_points (default: 200) | |
| top_n | No | Max query results (default: 10) | |
| units | No | JSON array of unit strings (unit_check) | |
| upper | No | Upper integration bound | |
| value | No | Value as string — integers, fractions (3/4), decimals (9.81) | |
| action | No | Operation within the selected tool. compute: add/subtract/multiply/divide/power/gcd/lcm/factorize/sqrt/trig/fraction/slide/unit_convert/unit_factor/unit_check/domain_check/list_units. reference: help/discover/guide/lookup/list_methods/list_domains/read_domain/recommend/list_entries/query_entries/db_stats/landmarks. model: define/extend/forward/observe/what_if/solve/learn/sensitivity. workspace: create/add/read/derive/update/link/gcd/lcm/lattice/ratios/query/cluster/snapshot/export/import/diff/note/notes/clear_notes. analyze: compare/verify/project/route/sensitivity. optimize: derivative/gradient/jacobian/hessian/taylor/integral/critical_points/tangent/curve_analysis/optimize/learn. | |
| domain | No | Domain prefix filter (list_entries, query_entries, landmarks) | |
| inputs | No | JSON array of inputs (domain_check) | |
| method | No | Method within module (guide — e.g. 'determinant', 'molar_mass') | |
| module | No | Domain module (guide, list_methods — e.g. 'matrix', 'chemistry') | |
| search | No | Name substring (query_entries) | |
| source | No | Data provenance (add) | |
| target | No | Note target: value name or 'field' | |
| values | No | JSON array of values (compute slide, workspace gcd/lcm/lattice/ratios) | |
| degrees | No | Angle in degrees (trig) | |
| targets | No | JSON targets: {output_name: target_value} (learn, optimize) | |
| to_unit | No | Target unit (unit_convert/unit_factor) | |
| updates | No | Input updates for forward: {input_name: 'new_value'} | |
| function | No | Trig function: sin/cos/tan/all/asin/acos/atan | |
| new_name | No | Name for derived result | |
| sig_figs | No | Significant figures (empty=exact) | |
| store_as | No | Store result in workspace with this name | |
| to_value | No | Target value (route) | |
| wrt_name | No | Differentiate with respect to | |
| dimension | No | Dimension name (list_units) | |
| from_unit | No | Source unit (unit_convert/unit_factor) | |
| intervals | No | Simpson's rule intervals (default: 1000) | |
| max_bound | No | Search bound for solve (default: 1000000) | |
| max_steps | No | Max gradient descent iterations (default: 20) | |
| operation | No | Operation to check (unit_check, domain_check) | |
| read_mode | No | Derive combination: multiply/divide/add/subtract/power/gcd/lcm/sin/cos/tan/log/exp/abs | |
| scenarios | No | What-if scenarios: [{name:str, updates:{input:value}}] | |
| tolerance | No | Convergence tolerance as fraction (e.g. '1/10000') | |
| tool_name | No | Tool name for help manual | |
| from_value | No | Starting value (route) | |
| identifier | No | Alternate query parameter (lookup) | |
| input_name | No | Input variable (solve, sensitivity) | |
| operations | No | Calculation steps: [{values:[str,str], read:'op', label:'name'}]. Reference previous: $prev, $label_name. | |
| search_max | No | Critical points search max (default: 100) | |
| search_min | No | Critical points search min (default: -100) | |
| snapshot_a | No | First snapshot (diff) | |
| snapshot_b | No | Second snapshot (diff) | |
| description | No | Natural language description (recommend) | |
| filter_type | No | Query filter: tag/domain/dimension/similar/precision | |
| output_name | No | Output variable (solve, derivative, gradient) | |
| filter_value | No | Query filter value | |
| output_names | No | JSON array of output names (sensitivity) | |
| target_value | No | Desired output value (solve) | |
| learning_rate | No | Gradient descent step size (default: 1/10) | |
| max_iterations | No | Max iterations for solve (default: 50) | |
| min_similarity | No | Clustering threshold (default: 0.5) | |
| snapshot_action | No | Snapshot op: save/restore/list/delete |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses behavioral traits beyond annotations: exact fractions, zero floating-point errors, constants from CODATA 2022 and IUPAC 2021, precision for transcendentals, and elimination of hallucination and token waste. Doesn't contradict annotations.
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?
The description is verbose, spanning multiple paragraphs and inline examples. While it is well-structured and front-loaded with purpose and guidelines, it could be more concise. The length may cause an agent to miss key details.
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?
Despite the complexity and 79 parameters, the description does not explain the return format or structure of responses for each subsystem. With no output schema, this is a gap. However, it does mention exact fractions and precision for functions.
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?
Schema coverage is 95%, so the schema already documents most parameters. The description adds some context for the 'tool' parameter with examples and subsystem descriptions, but little additional meaning for individual parameters beyond what the schema provides. Meets baseline.
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 clearly states it is the default calculation engine for numeric computations, listing many specific operations (arithmetic, unit conversion, etc.) and contrasting with mental math or Python. It distinguishes itself from siblings by emphasizing it's the go-to for computations where the answer is the goal.
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?
Explicitly provides when to use Arithym vs Python/analysis tool with concrete examples: 'any calculation where the answer itself is the goal' vs 'algorithmic work where code is the goal'. Also mentions when to avoid it (data transformations, plotting, etc.).
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!
Your Connectors
Sign in to create a connector for this server.