Skip to main content
Glama
111-test-111

Math MCP Server

by 111-test-111

create_and_save_chart

Create and save statistical charts (line, bar, pie, histogram, scatter, box, heatmap, correlation, multi-series) from data, with customizable labels, colors, and styles.

Instructions

Brief description: Data visualization and chart creation tool, supporting various statistical chart types.
Examples:
    create_and_save_chart(chart_type='line', x_data=[1,2,3,4], y_data=[1,4,2,3], title='Line Plot')
    create_and_save_chart(chart_type='histogram', data=[1,2,2,3,3,3,4,4,5], filename='histogram_plot')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_typeYesChart type. Supports: 'bar', 'pie', 'line', 'scatter', 'histogram', 'box', 'heatmap', 'correlation_matrix', 'multi_series_line'
dataNoSingle series data for bar, pie, histogram, box plots
x_dataNoX-axis data for line, scatter, multi-series line plots
y_dataNoY-axis data for line, scatter plots
y_data_seriesNoMulti-series Y-axis data for multi-series line plots
series_labelsNoLabels for multi-series plots
matrix_dataNoMatrix data for heatmaps, correlation matrices
labelsNoData labels for bar charts, pie charts
titleNoChart titleStatistical Chart
xlabelNoX-axis labelX Axis
ylabelNoY-axis labelY Axis
filenameNoSave filename without path and extension
formatNoImage format. Supports: 'png', 'jpg', 'svg'png
colorsNoList of custom colors for chart elements
figsizeNoFigure size as (width, height)
dpiNoImage resolution
styleNoChart stylewhitegrid
timestampNoWhether to add timestamp to filename
show_valuesNoWhether to display value labels on bar charts
horizontalNoWhether to create horizontal bar chart
trend_lineNoWhether to display trend line on scatter plots
trend_line_colorNoTrend line color
trend_line_equationNoTrend line equation text
binsNoNumber of bins for histogram
annotateNoWhether to display numerical annotations on heatmaps
colormapNoColormap for heatmapsviridis
colorNoSingle color
line_widthNoLine width for line plots
line_styleNoLine style-
markerNoMarker styleo
marker_sizeNoMarker size
alphaNoTransparency level
gridNoWhether to display grid
Behavior2/5

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

No annotations provided; description does not mention side effects, permissions, or that the tool saves charts to files. The filename parameter implies saving, but this is not explicit.

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 short with a brief line and examples, making it concise. However, it lacks sections or structure, which could improve readability.

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?

With 33 parameters and no output schema, the description is too minimal. It fails to explain save behavior, return values, or how parameters interact for different chart types.

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%, so parameters are already documented. The description adds examples but does not explain parameter combinations or chart type specifics beyond the schema.

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 it is a data visualization and chart creation tool with examples. However, it does not differentiate from sibling tools like 'plot_function_curve', which may also produce plots.

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 this tool versus alternatives. The description only provides examples but lacks explicit context for selection.

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