Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_solve

Solve algebraic equations or systems of equations using symbolic mathematics. Input an equation and optionally specify variables to solve for.

Instructions

Solve an equation or system of equations.

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": {
      "equation": "<equation>"
    },
    "name": "sympy_solve"
  }
}

Input Schema

NameRequiredDescriptionDefault
equationYesString equation
variablesNoComma-separated variables to solve for

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as whether solutions are symbolic, output format, or handling of multiple equations. It does not add this context.

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 concise—one clear sentence—but could benefit from a bit more detail without being verbose.

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 tool's complexity (solving equations) and the lack of output schema details in the prompt, the description is too sparse, missing information about input format for systems and the nature of solutions.

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%, so the description does not need to add meaning; the schema already describes equation and variables. The description adds no additional value.

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 'Solve an equation or system of equations' clearly states the action (solve) and the resource (equation or system), distinguishing it from many siblings, though sympy_solveset also solves equations.

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 this tool versus alternatives like sympy_solveset or sympy_nsolve, nor on prerequisites or limitations.

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