Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_roots

Find the roots of any polynomial expression using symbolic computation. Specify the variable to get exact solutions.

Instructions

Find roots of polynomial.

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": {
      "expr": "<expr>"
    },
    "name": "sympy_roots"
  }
}

Input Schema

NameRequiredDescriptionDefault
exprYesPolynomial expression
variableNoVariablex

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?

No annotations provided, so description carries full burden. It only says 'Find roots', lacking details on output format (e.g., returns list of roots, whether multiplicities are included, domain).

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?

Single sentence with no filler. Could be improved with a brief second sentence for context, but remains concise and front-loaded.

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 existence of output schema, description need not detail return values. However, lacks context on root types (real/complex), handling of non-polynomial inputs, and error conditions. Adequate but not thorough.

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 covers both parameters with descriptions ('Polynomial expression', 'Variable'). Description does not add extra meaning beyond schema, but baseline is 3 due to 100% coverage.

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 finds roots of a polynomial. It distinguishes itself from siblings like sympy_solve (general equation solving) and sympy_solveset (set solving), but could be more specific about symbolic vs numeric roots.

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 sympy_roots over alternatives (e.g., sympy_solve). No mention of prerequisites or limitations (e.g., works only for polynomials).

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