Skip to main content
Glama
sktime

sktime-mcp

Official
by sktime

plot_series

Visualize time series data by plotting one or multiple series with customizable labels, titles, and figure settings. Save plots as PNG, SVG, or WebP, or retrieve as base64 for integration.

Instructions

Plot one or more time series natively. Can save the plot to a specified path as a PNG file or return it as a base64 string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dpiNoResolution in dots per inch (default: 150).
pathNoOptional local file path to save the plot (e.g., '/tmp/plot.png'). If omitted, returns base64.
titleNoOptional title for the plot.
labelsNoOptional list of labels corresponding to each data handle.
figsizeNoFigure size as [width, height] in inches (default: [12, 6]).
markersNoMarker style(s) for data points (e.g., 'o', ['.', 'x']).
x_labelNoCustom x-axis label.
y_labelNoCustom y-axis label.
data_handlesYesList of data handle IDs to plot (e.g., train, test, forecasts).
image_formatNoImage output format: 'png' (default), 'svg', or 'webp'.png
Behavior2/5

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

Lacking annotations, the description only mentions saving to PNG or returning base64. It does not disclose whether it modifies data, required permissions, performance impact, or error behavior. Critical behavioral traits are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences that front-load the core purpose ('Plot one or more time series natively') and efficiently cover output options. No wasted words.

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?

Despite 10 parameters and no output schema, the description omits important context like return structure (base64 string details), error handling, or constraints on data formats. Incomplete for a tool with many options.

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 all parameters described. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 specifies the action ('plot') and resource ('time series'), and distinguishes from sibling tools like 'inspect_data' or 'evaluate_estimator' which have different purposes.

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, nor any context on prerequisites or exclusions. The description solely states what it does without aiding decision-making.

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/sktime/sktime-mcp'

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