Skip to main content
Glama
111-test-111

Math MCP Server

by 111-test-111

matrix_calculator

Perform matrix calculations and linear algebra analysis including addition, multiplication, eigenvalues, decomposition, and system solving.

Instructions

Brief description: Matrix and linear algebra calculation tool, supporting basic operations and advanced analysis.
Examples:
    matrix_calculator(operation='multiply', matrix_a=[[1,2],[3,4]], matrix_b=[[5,6],[7,8]])
    matrix_calculator(operation='eigenvalues', matrix_a=[[4,2],[1,3]])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesMatrix operation type. Supports: 'add', 'subtract', 'multiply', 'transpose', 'determinant', 'inverse', 'rank', 'eigenvalues', 'eigenvectors', 'norm', 'trace', 'decomposition', 'solve_system', 'properties'
matrix_aYesPrimary matrix as a 2D list
matrix_bNoSecondary matrix as a 2D list. Required for binary operations
methodNoMethod for decomposition. Supports: 'lu', 'qr', 'svd', 'cholesky'
powerNoPower for matrix exponentiation
property_typeNoType of matrix property to analyze. Supports: 'all', 'basic', 'advanced'
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as side effects, error handling, or performance characteristics. It only mentions 'basic operations and advanced analysis' without further elaboration.

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

Conciseness3/5

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

The description is concise but overly minimal for a complex tool with six parameters. It consists of one sentence and two examples, which is front-loaded but insufficient.

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 the tool's complexity (6 parameters, no output schema, no annotations), the description lacks completeness. It does not explain return values, result format, or edge cases.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already describes all parameters. The description does not add new meaning beyond repeating operation examples.

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

Purpose5/5

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

The description explicitly identifies the tool as a 'Matrix and linear algebra calculation tool', which is a clear and specific verb+resource. It distinguishes from siblings like basic_arithmetic and calculus_engine.

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?

No explicit when-to-use or when-not-to-use guidance is given. The context of matrix operations is implied, but no alternatives are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/111-test-111/math-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server