Skip to main content
Glama
deenesjakoruzh
githejie

Calculator MCP Server

by githejie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Калькулятор MCP Сервер

Сервер Model Context Protocol для вычислений. Этот сервер позволяет LLM использовать калькулятор для точных числовых вычислений.

Доступные инструменты

  • calculate - Вычисляет/оценивает заданное выражение.

    • expression (строка, обязательно): Выражение для вычисления

Установка

Использование УФ (рекомендуется)

При использовании uv не требуется специальной установки. Мы будем использовать uvx для непосредственного запуска mcp-server-calculator .

curl -LsSf https://astral.sh/uv/install.sh | sh

Использование PIP-картинки

В качестве альтернативы вы можете установить mcp-server-calculator через pip:

pip install mcp-server-calculator

После установки вы можете запустить его как скрипт, используя:

python -m mcp_server_calculator

Related MCP server: Calculator MCP

Конфигурация

Использование УФ (рекомендуется)

Добавьте это в настройки вашего клиента MCP:

"mcpServers": {
  "calculator": {
    "command": "uvx",
    "args": ["mcp-server-calculator"]
  }
}

Использование PIP-картинки

Либо добавьте это в настройки клиента MCP:

"mcpServers": {
  "calculator": {
    "command": "python",
    "args": ["-m", "mcp_server_calculator"]
  }
}

Лицензия

mcp-server-calculator лицензируется по лицензии MIT. Это означает, что вы можете свободно использовать, изменять и распространять программное обеспечение в соответствии с условиями лицензии MIT. Для получения более подробной информации см. файл LICENSE в репозитории проекта.

Available Tools

1 tool
calculateD

Calculates/evaluates the given expression.

ParametersJSON Schema
NameRequiredDescriptionDefault
expressionYes

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning any traits like error handling, performance limits, output format, or side effects. This leaves the agent with insufficient information about how the tool behaves beyond its basic function.

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 very concise with a single sentence, which is efficient and front-loaded. However, it is overly brief to the point of under-specification, lacking necessary details that would make it more helpful without becoming verbose.

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

Completeness1/5

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

Given the tool's complexity (a calculation function with no annotations, no output schema, and low schema coverage), the description is incomplete. It fails to address key aspects like return values, error cases, or usage examples, making it inadequate for an agent to effectively invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the description does not compensate by explaining what 'expression' entails (e.g., syntax, supported operators, constraints). This leaves the parameter semantics entirely undocumented, failing to add value beyond the minimal schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Calculates/evaluates the given expression' is tautological, essentially restating the tool name 'calculate' without adding specificity. It mentions a verb ('calculates/evaluates') and resource ('expression'), but lacks details about what type of expressions are supported or the calculation context, making it vague.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool, such as for mathematical expressions, logical evaluations, or specific domains. Since there are no sibling tools, the lack of alternatives doesn't penalize heavily, but the description fails to offer any contextual usage hints or prerequisites.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedcalculate
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

C2.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools; the single tool 'calculate' has a distinct and clear purpose for evaluating expressions.

Naming Consistency5/5

The single tool name 'calculate' follows a consistent verb-based pattern, and with only one tool, there is no inconsistency in naming conventions to evaluate.

Tool Count2/5

A single tool for a calculator server feels thin and under-scoped, as it lacks operations for common mathematical functions (e.g., add, subtract, trigonometric functions) or advanced features, making it borderline too few for the domain.

Completeness2/5

The tool surface is severely incomplete for a calculator domain; it only provides a generic 'calculate' tool without covering basic arithmetic operations, scientific functions, or memory features, leading to significant gaps in functionality.

Maintenance

ActivityStale
ResponsivenessResponsive

Resources

Related MCP Connectors

Related MCP Servers

  • Math-MCP

    EthanHenrickson
    A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol server that provides basic mathematical and statistical functions to LLMs, enabling them to perform accurate numerical calculations through a simple API.
    13
    11 npm
    186
    MIT

  • Calculator MCP

    wrtnlabs
    A
    license
    B
    quality
    C
    maintenance
    A Model Context Protocol server that provides basic calculator functionality for LLMs, enabling them to perform mathematical operations like addition, subtraction, multiplication, division, modulo, and square root.
    6
    235 npm
    15
    MIT

  • Calculator MCP Server

    functicons
    A
    license
    Not graded
    quality
    D
    maintenance
    A backend service that provides accurate arithmetic calculation capabilities to AI models via the Model Context Protocol, allowing LLMs to offload mathematical computations for numerical queries.
    1
    MIT

Appeared in Searches