Skip to main content
Glama
daedalus

mcp-sympy

by daedalus
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

sympy_Identity

Generate an n x n identity matrix for symbolic linear algebra computations.

Instructions

Identity matrix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • src/mcp_sympy/tools.py:2414-2417 (handler)
    The tool handler function for 'sympy_Identity'. It is decorated with @mcp.tool(), takes an integer n, and returns a string representation of sympy.Identity(n).
    @mcp.tool()
def sympy_Identity(n: int) -> str:
    """Identity matrix."""
    return str(sympy.Identity(n))
  • src/mcp_sympy/tools.py:2414-2414 (registration)
    The @mcp.tool() decorator registers this function as an MCP tool with the FastMCP server instance.
    @mcp.tool()

Tool Definition Quality

D1.5/5.0
Behavior1/5

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

Annotations are absent, so the description bears full responsibility. It only states 'Identity matrix' with no information about return type, side effects, mutability, or permissions. This is insufficient for safe invocation.

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 (two words), which is concise but severely under-specified. It sacrifices necessary detail for brevity.

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?

Given the tool has one parameter and an output schema, the description should at least state that the output is an n x n identity matrix. The current description is too minimal to be complete.

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 schema has 0% description coverage for parameters. The description does not explain that `n` is the dimension of the square identity matrix. Without this, the agent cannot know the parameter's meaning.

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?

Description is a noun phrase without a verb; it identifies the resource but does not clearly state the action (returns, creates). It vaguely distinguishes the identity matrix from other matrices, but fails to explicitly differentiate from siblings like `sympy_eye`, `sympy_ones`, etc.

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 use this tool versus alternatives. For example, it does not mention that `sympy_Identity` should be used to create a square matrix with ones on the diagonal, nor does it discuss when to use `sympy_eye` (if different) or other matrix creation tools.

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/daedalus/mcp-sympy'

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