Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_matrix_nullspace

Compute the nullspace of a symbolic matrix using SymPy. Returns basis vectors for the nullspace.

Instructions

Nullspace.

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": "<matrix>"
    },
    "name": "sympy_matrix_nullspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations provided, the description must carry the full burden of behavioral transparency, but it is absent. The tool does not disclose whether the input must be a square matrix, whether it handles symbolic matrices, or what the output represents.

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

Conciseness2/5

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

The description is extremely short but at the cost of essential detail; it is under-specified rather than properly concise, providing no structural guidance.

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?

Even with an output schema present, the description fails to convey the type of matrix accepted or the nature of the nullspace computation, making it insufficient for correct invocation.

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 a single string parameter 'matrix' with no description, and the tool description does not clarify the expected format (e.g., SymPy matrix string, nested list), leaving the agent to infer.

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 'Nullspace.' is a tautology of the tool name, providing no additional context about what the tool does or how it differs from sibling matrix operations like sympy_matrix_eigenvects.

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

Usage Guidelines1/5

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

No usage guidelines are provided; the description does not indicate when to use this tool versus alternatives such as sympy_matrix_eigenvects or sympy_matrix_rank, nor any prerequisites.

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