Skip to main content
Glama

sympy_ne

Construct a symbolic inequality representing not equal between two mathematical expressions.

Instructions

Create inequality (not equal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lhsYesLeft-hand side
rhsYesRight-hand side

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for the 'sympy_ne' tool. Decorated with @mcp.tool(), it creates a SymPy Ne (not equal) expression from two string inputs using _sympify() and returns it as a string.
    @mcp.tool()
    def sympy_ne(lhs: str, rhs: str) -> str:
        """Create inequality (not equal).
    
        Args:
            lhs: Left-hand side
            rhs: Right-hand side
    
        Returns:
            Neq as string
    
        Example:
            >>> sympy_ne("x", "y")
            "Ne(x, y)"
        """
        return str(Ne(_sympify(lhs), _sympify(rhs)))
  • The _sympify helper function converts string expressions to SymPy objects, used by sympy_ne to parse input.
    def _sympify(expr: str) -> sympy.Basic:
        """Convert string expression to SymPy object."""
        return sympy.sympify(expr)
  • The Ne symbol is imported from sympy at line 29, the core 'Not Equal' class used by sympy_ne.
    Ne,
  • The @mcp.tool() decorator registers sympy_ne as an MCP tool with the FastMCP server (mcp-sympy).
    @mcp.tool()
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'create' without indicating whether the operation is read-only, returns a symbolic expression, or any side effects. The agent lacks context on what 'create' entails.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loads the core purpose. However, it could be slightly expanded to include usage hints without losing conciseness.

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

Completeness3/5

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

Given an output schema exists (unknown content) and the tool is simple, the description is minimal but sufficient. However, it does not clarify that the result is a symbolic inequality expression, which could be expected from a sympy tool.

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?

The input schema already provides full parameter descriptions (lhs and rhs). The description adds the context of 'not equal' but does not enhance parameter understanding beyond the schema. Baseline 3 for high schema coverage.

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 'Create inequality (not equal)' clearly states the action and the specific type of inequality. It distinguishes from sibling tools like sympy_eq (equality) and other comparisons.

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?

The description does not provide any guidance on when to use this tool versus alternatives. For example, it does not mention that sympy_eq should be used for equality or that sympy_lt/gt are for strict comparisons.

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