Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_checkodesol

Check whether a proposed function satisfies an ordinary differential equation by substituting into the ODE.

Instructions

Check ODE solution.

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": {
      "eq": "<eq>",
      "sol": "<sol>"
    },
    "name": "sympy_checkodesol"
  }
}

Input Schema

NameRequiredDescriptionDefault
eqYes
solYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior1/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not state whether the tool returns a boolean, modifies state, or requires specific permissions, nor does it describe edge cases or limitations.

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 very concise at one sentence, but it is not overly verbose. However, it sacrifices necessary detail for brevity, which reduces overall effectiveness.

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?

Given the existence of an output schema, the description does not need to explain return values, but it still fails to provide enough context for an AI agent to correctly select and invoke the tool. It omits critical details like whether the tool returns a boolean or a detailed result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not explain the parameters 'eq' and 'sol'. While 'Check ODE solution' implies eq is the ODE and sol is the candidate solution, this is left to inference. No details on format or expected types are given.

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 'Check ODE solution' clearly states the verb (check) and resource (ODE solution), but lacks specificity about what 'check' entails (e.g., verifying if the solution satisfies the ODE) and does not differentiate from siblings like sympy_classify_ode or sympy_dsolve.

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 usage guidance is provided. The description does not indicate when to use this tool over alternative ODE-related tools, nor does it mention prerequisites or expected input formats.

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