Skip to main content
Glama

sympy_classify_ode

Classify an ordinary differential equation (ODE) by specifying the equation and dependent variable.

Instructions

Classify ODE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eqYes
funcYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the sympy_classify_ode tool. It takes an ODE equation string and a function string, converts them to SymPy objects via _sympify, then calls sympy.classify_ode and returns the result as a string.
    @mcp.tool()
    def sympy_classify_ode(eq: str, func: str) -> str:
        """Classify ODE."""
        return str(sympy.classify_ode(_sympify(eq), _sympify(func)))
  • The @mcp.tool() decorator registers the sympy_classify_ode function as an MCP tool with the FastMCP server.
    @mcp.tool()
  • Helper utility that converts a string expression into a SymPy object using sympy.sympify. Used by sympy_classify_ode to parse input strings.
    def _sympify(expr: str) -> sympy.Basic:
        """Convert string expression to SymPy object."""
        return sympy.sympify(expr)
  • The FastMCP server instance that provides the @mcp.tool() decorator for registration.
    mcp = fastmcp.FastMCP("mcp-sympy")
Behavior1/5

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

No annotations provided. Description fails to disclose what 'classify' entails, output format, or any behavioral traits beyond the bare minimum.

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?

Extremely concise at two words, but this is under-specification rather than efficient communication. Does not earn its place.

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?

Despite the presence of an output schema, the description is insufficient for an agent to understand the input requirements and behavior of this ODE classification tool.

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?

Schema has 0% description coverage, and the description provides no explanation of what 'eq' or 'func' represent. Adds no value beyond the parameter names.

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?

Clearly states the action ('Classify') and the resource ('ODE'). Distinguishes from related tools like sympy_dsolve and sympy_checkodesol.

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 like dsolve or checkodesol. Does not mention prerequisites or context.

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