Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_matrix_add

Add two matrices by providing their string representations for symbolic computation.

Instructions

Add two matrices.

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": {
      "matrix1": "<matrix1>",
      "matrix2": "<matrix2>"
    },
    "name": "sympy_matrix_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrix1YesFirst matrix string
matrix2YesSecond matrix string

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description bears full burden for disclosing behavior. It only states 'Add two matrices,' omitting details on matrix size compatibility, error handling, or output format. The agent cannot infer important behavioral traits.

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 extremely concise (one sentence) but lacks structure. While front-loaded, it sacrifices necessary details for brevity. A slightly longer description would improve completeness without harming conciseness.

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 existence of an output schema and multiple sibling tools, the description should explain return values or provide context on matrix representation. It is too minimal to be considered complete for an agent to use confidently.

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 descriptions ('First matrix string', 'Second matrix string') are minimal and add little meaning beyond parameter names. The tool description does not elaborate on valid matrix string format, making it insufficient for proper parameter construction.

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 description 'Add two matrices' clearly states the verb (Add) and resource (two matrices), distinguishing it from siblings like matrix multiplication or determinant. However, it does not specify input format, but the input schema clarifies that parameters are strings.

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 versus alternatives such as sympy_matrix_multiply or sympy_matrix_transpose. The description simply implies addition, but lacks explicit when-to-use or when-not-to-use information.

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