Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_expand

Expand algebraic expressions symbolically using SymPy. Provide a string expression to compute its expanded form.

Instructions

Expand an expression.

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_expand"
  }
}

Input Schema

NameRequiredDescriptionDefault
exprYesString expression to expand

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It only states 'Expand an expression,' omitting any details about side effects, permissions, or output behavior. The user must infer that this is a safe, mathematical transformation.

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?

The description is extremely short (3 words), but this comes at the cost of missing critical context. It is not appropriately sized; it should include at least a hint about the kind of expansion to aid differentiation.

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 cover return values. However, with a single parameter and many sibling tools, the description is too generic. An agent cannot determine when to use this expand versus other expand variants, making it incomplete for the complexity of the environment.

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 description coverage is 100% (parameter 'expr' described as 'String expression to expand'). The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Expand an expression' clearly states the action and resource, but fails to differentiate from sibling tools like sympy_expand_complex, sympy_expand_log, and sympy_expand_trig. It does not specify the type of expansion (e.g., algebraic), making it ambiguous which tool to use.

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. With many similar expansion and simplification siblings (sympy_simplify, sympy_factor, sympy_apart), the description offers no selection criteria.

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