Skip to main content
Glama
ghostiee-11

holoviz-viz-mcp

by ghostiee-11

create_plot

Create interactive plots from loaded datasets with support for scatter, line, bar, and many more chart types. Generates both a PNG preview and interactive HTML output.

Instructions

Create an interactive plot from a loaded dataset.

Returns both a PNG preview (for inline chat display) and interactive HTML (as an embedded resource for full interactivity).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesColumn name for x-axis
yNoColumn name for y-axis (optional for hist/kde)
themeNoVisual theme — None (default), 'dark', 'midnight'
titleNoPlot title
widthNoPlot width in pixels (default 700)
heightNoPlot height in pixels (default 450)
size_byNoColumn name to size points by (scatter only)
color_byNoColumn name to color points/bars by
group_byNoColumn name to create separate subplots by
plot_typeYesType — scatter, line, bar, barh, area, step, box, violin, hist, heatmap, hexbin, kde, contour, errorbars
dataset_nameYesName of the loaded dataset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It mentions the output types but lacks details on side effects, resource usage, or prerequisites beyond 'loaded dataset'. Adequate but not comprehensive.

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 primary purpose and then detail the output. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (11 params, many siblings) and presence of output schema, the description adequately covers the main action and return format. Minor omission: doesn't explain if plot is persisted for later modification.

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 the description adds no additional parameter meaning beyond what the schema already provides. Baseline 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 states the tool creates an interactive plot from a loaded dataset and distinguishes it from siblings by specifying the dual output (PNG preview and interactive HTML).

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 like create_datashader_plot or modify_plot. The description does not provide context for selection among sibling tools.

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/ghostiee-11/holoviz-viz-mcp'

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