Skip to main content
Glama
Sign In
Mathematical Calculator MCP Server

Mathematical Calculator MCP Server

by Chetto983
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

matrix_addition

Add two matrices by providing matching lists of lists; returns the summed matrix or an error if dimensions are incompatible.

Instructions

Adds two matrices.

Args: matrix_a: The first matrix as a list of lists. matrix_b: The second matrix as a list of lists.

Returns: On success: {"result": } On error: {"error": }

Examples: >>> matrix_addition([[1, 2], [3, 4]], [[5, 6], [7, 8]]) {'result': [[6, 8], [10, 12]]}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matrix_a": "<matrix_a>",
      "matrix_b": "<matrix_b>"
    },
    "name": "matrix_addition"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrix_aYes
matrix_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the response envelope ('On success: {"result": ...}' / 'On error: {"error": ...}'), which is valuable since there is no output schema. However, it omits any constraint that the two matrices must have matching dimensions, which is the main failure mode an agent needs to know about.

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?

Front-loaded one-line purpose followed by clearly labeled Args, Returns, and Examples sections. Every block earns its place; the Args lines are slightly redundant with the schema types but cheap.

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?

With no annotations and no output schema, the description supplies the missing pieces: argument shape and the success/error return contract, backed by an example. The only meaningful omission is behavior on mismatched matrix dimensions.

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?

Schema description coverage is 0%, so the description must compensate, and it does: both parameters are named with their expected shape ('as a list of lists'), and the worked example makes the accepted nesting and numeric element type concrete. It adds useful meaning beyond the bare array-of-array schema.

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

Purpose4/5

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

The first line states a specific verb and resource: 'Adds two matrices.' Combined with the tool name, an agent can immediately distinguish this from matrix_multiplication, matrix_transpose, and matrix_determinant without opening a schema. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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?

Usage is only implied by the operation itself – the description never states when to pick addition over the other matrix or vector tools, nor any preconditions. For a trivial, unambiguous math operation this is adequate but not instructive.

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

Deploy Server

Other Tools