CALCULATE_MCP

calculate_matrix

Performs matrix arithmetic: add, subtract, multiply, transpose, determinant, inverse, and solve Ax=b. Provides deterministic results for linear algebra tasks.

Instructions

Matrix arithmetic: add, subtract, multiply, transpose, determinant, inverse, and solve Ax=b.

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": {
      "operation": "<operation>",
      "a": "<a>"
    },
    "name": "calculate_matrix"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	No
`operation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 14, 2026

TDQS

C2.8/5.0

Behavior2/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 names the operations but omits constraints such as required square matrices for determinant/inverse, error behavior, return format, or numerical precision.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the colon and list are efficient.

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

Completeness2/5

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

Given no annotations, no output schema, and 0% schema description coverage, the description is too thin for a 7-operation matrix tool. It should specify which parameters each operation needs and key constraints.

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

Parameters2/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. It repeats the operation enum values and clarifies 'solve Ax=b' to link a and b for that operation, but it does not explain parameter roles for the other operations, required/optional status, or shapes.

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?

States a specific resource (matrix) and enumerates the operations, so an agent can tell it is the matrix-arithmetic tool rather than a general expression evaluator. It does not explicitly name or differentiate from any sibling, so it stops short of a 5.

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 on when to choose this tool over calculate_expression or other calculators; the operations are listed but no scenarios, prerequisites, or exclusions are given. Implied usage only.

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

Deploy Server