Skip to main content
Glama
111-test-111

Math MCP Server

by 111-test-111

complex_analysis_suite

Convert complex numbers, calculate residues, perform analytic continuation, and visualize complex planes. Supports arithmetic, contour integration, series expansion, and more.

Instructions

Brief description:
    Powerful complex analysis and complex function tool, supporting complex number form conversion, residue calculation, analytic continuation, complex plane visualization, and other advanced features.
Examples:
    complex_analysis_suite(operation='convert_form', complex_number='3+4i')
    complex_analysis_suite(operation='function_evaluation', function_expression='z**2 + 1', complex_number='1+i')
    complex_analysis_suite(operation='residue_calculation', function_expression='1/(z**2 + 1)', singularities=['i', '-i'])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesComplex analysis operation. Supports: 'arithmetic', 'complex_functions', 'contour_integration', 'residue_calculation', 'series_expansion', 'visualization'
complex_numberNoSingle complex number (string or complex type)
complex_numbersNoList of complex numbers for operations
function_expressionNoComplex function expression
variableNoComplex variable symbolz
contour_pointsNoContour points for integration
singularitiesNoList of function singularities
centerNoCenter point for expansion
radiusNoRadius for convergence
orderNoOrder of expansion or pole
x_rangeNoReal axis range for visualization
y_rangeNoImaginary axis range for visualization
resolutionNoPlot resolution
colormapNoColormap for visualizationhsv
filenameNoOutput filename for plots
plot_typeNoVisualization type. Supports: 'domain_coloring', 'contour_plot', 'surface_plot'domain_coloring
series_termsNoNumber of series terms
branch_cutNoBranch cut specification
methodNoCalculation methodauto
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only gives a high-level feature list without mentioning side effects, performance implications, or error handling. The tool could modify resources or have destructive behaviors, but nothing is stated.

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 brief, with only 3 sentences and three examples. It front-loads key features and uses a structure that is easy to scan. The first sentence could be more precise, but overall it is concise for a tool with 19 parameters.

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 (19 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values, covers only a subset of operations in examples, and fails to address how parameters interact or what happens with invalid inputs.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds three examples that illustrate parameter combinations, which provides some extra context. However, it does not clarify parameter relationships or constraints beyond the schema definitions.

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 identifies the tool as a complex analysis suite, mentioning specific features like form conversion and residue calculation. However, there is a mismatch between the described features (e.g., 'analytic continuation') and the actual operation categories listed in the schema, making the purpose slightly ambiguous.

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?

The description provides no explicit guidance on when to use this tool versus its siblings (e.g., basic_arithmetic, plot_function_curve). It does not state prerequisites or situations where alternative tools are more appropriate, leaving the agent without decision-making support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/111-test-111/math-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server