Skip to main content
Glama
111-test-111

Math MCP Server

by 111-test-111

plot_function_curve

Plot mathematical functions with optional derivative visualization and critical points. Customize graph style, range, and output format.

Instructions

Brief description: Mathematical function curve plotting tool, supporting function graph visualization and derivative analysis.
Examples:
    plot_function_curve(function_expression='x**2 + 2*x + 1')
    plot_function_curve(function_expression='sin(x)', x_range=(-6.28, 6.28), filename='sine_wave')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
function_expressionYesFunction expression with common math functions like sin, cos, exp, log, sqrt
variableNoIndependent variable namex
x_rangeNoX-axis range as (min_value, max_value)
num_pointsNoNumber of plotting points
titleNoChart titleFunction Graph
xlabelNoX-axis labelX Axis
ylabelNoY-axis labelY Axis
filenameNoSave filename without path and extension
formatNoImage format. Supports: 'png', 'jpg', 'svg'png
figsizeNoFigure size as (width, height)
dpiNoImage resolution
colorNoFunction curve colorblue
line_widthNoLine width
gridNoWhether to display grid
grid_alphaNoGrid transparency
derivative_orderNoDerivative order for plotting n-th derivative curve
show_critical_pointsNoWhether to show critical points (extrema)
show_equationNoWhether to display function equation on plot
equation_positionNoEquation display position. Supports: 'upper right', 'upper left', 'lower right', 'lower left'upper right
alphaNoLine transparency
line_styleNoLine style-
markerNoData point marker
marker_sizeNoMarker size
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It mentions derivative analysis but does not disclose what the tool returns (e.g., saves an image, displays plot, returns file path), error handling, or side effects. The examples suggest saving a file, but the behavior is not described in prose.

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 with two lines and two examples, but it includes the redundant phrase 'Brief description'. The examples provide clear usage patterns. Overall, it is efficient but could be more structured with bullet points or a clearer separation of behavior and 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 (23 parameters, 1 required), the description is insufficient. It does not explain what the tool outputs (e.g., file path, image data), how to handle derivative orders, or provide context for advanced features like critical points. The examples help but are not comprehensive.

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 schema has 100% description coverage, so the baseline is 3. The description adds no additional meaning beyond the schema; it only repeats the tool's high-level purpose. For instance, derivative analysis is mentioned but not linked to the 'derivative_order' parameter.

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

Purpose5/5

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

The description clearly states the tool's purpose: plotting mathematical function curves and supporting derivative analysis. It uses a specific verb ('plot') and resource ('mathematical function curve'), and the examples reinforce this. The sibling tools include more generic charting and calculus tools, but the description effectively distinguishes this tool.

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 does not provide any guidance on when to use this tool versus alternatives like 'calculus_engine' for derivative calculations or 'create_and_save_chart' for general plotting. There is no mention of prerequisites, limitations, or explicit when-to-use scenarios.

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