Skip to main content
Glama
Sign In
mcp-sympy

mcp-sympy

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sympy_powsimp

Simplify mathematical expressions by combining exponent rules and reducing powers to their simplest form. Solve complex power expressions easily.

Instructions

Simplify powers in 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_powsimp"
  }
}

Input Schema

NameRequiredDescriptionDefault
exprYesString expression with powers

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 are present, so the description must fully disclose behavior. It only states the basic operation without detailing side effects, return format, or edge cases (e.g., what happens with no powers). This is inadequate for agent decision-making.

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 extremely concise at one sentence, with no wasted words. It is front-loaded with the key action. However, it sacrifices completeness for brevity, resulting in a slight penalty.

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 the single parameter and the existence of an output schema, the description is minimally adequate but lacks details on the specific type of power simplification (e.g., combining exponents, applying logarithmic identities). In a large sibling set, more context would improve agent selection.

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% with a description for the single parameter 'expr'. The tool description adds minimal meaning beyond the schema, simply echoing 'simplify powers'. Baseline 3 applies as the schema already handles parameter documentation.

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 simplifies powers in an expression, specifying the verb 'simplify' and the resource 'powers'. It differentiates from the broader sympy_simplify tool by focusing on powers, but does not explicitly contrast with siblings like sympy_expand or sympy_radsimp.

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 (e.g., sympy_simplify, sympy_expand). The agent must infer usage from the name alone, which is insufficient for distinguishing between similar simplification tools.

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