Skip to main content
Glama

sympy_Nor

Computes the logical NOR of comma-separated symbolic expressions, returning the negation of the logical OR.

Instructions

Logical NOR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYesComma-separated expressions

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The sympy_Nor tool handler: decorated with @mcp.tool(), it parses a comma-separated string of expressions using _sympify and returns the result of sympy's Nor() as a string.
    @mcp.tool()
    def sympy_Nor(args: str) -> str:
        """Logical NOR.
    
        Args:
            args: Comma-separated expressions
    
        Returns:
            Nor as string
    
        Example:
            >>> sympy_Nor("False, False")
            "True"
        """
        return str(Nor(*[_sympify(a) for a in args.split(",")]))
  • Registration via @mcp.tool() decorator on the mcp = fastmcp.FastMCP('mcp-sympy') instance (line 119).
    @mcp.tool()
    def sympy_Nor(args: str) -> str:
  • Docstring describing args parameter as comma-separated expressions and return as Nor string.
    """Logical NOR.
    
    Args:
        args: Comma-separated expressions
    
    Returns:
        Nor as string
  • The _sympify helper function used by sympy_Nor to convert string expressions to SymPy objects.
    def _sympify(expr: str) -> sympy.Basic:
        """Convert string expression to SymPy object."""
        return sympy.sympify(expr)
  • FastMCP instance creation (mcp) that provides the @mcp.tool() decorator used to register sympy_Nor.
    mcp = fastmcp.FastMCP("mcp-sympy")
Behavior2/5

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

No annotations exist, so the description must carry the burden. It does not disclose behavioral traits such as whether it works on booleans, how it handles non-boolean arguments, or any side effects. The operation is implied but not elaborated.

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 very concise sentence that directly states the purpose. It is appropriately sized for such a simple tool, though a bit more detail would not hurt.

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?

Despite having an output schema, the description does not mention return behavior or result type. For a logical operation, understanding the output (boolean? expression?) is important. The description feels incomplete.

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% with one parameter 'args' described as 'Comma-separated expressions'. The description adds no further semantics beyond the schema, which is already adequate. Baseline score of 3 applies.

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 clearly states the tool implements 'Logical NOR', which is a specific logical operation. It is distinguished from siblings like sympy_And, sympy_Or, sympy_Nand by its unique name and operation, but could be more explicit about inputs and outputs.

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 NOR versus alternatives like NAND, NOT, OR. The description is a bare definition without context for selection.

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