Skip to main content
Glama
ghostiee-11

holoviz-viz-mcp

by ghostiee-11

create_streaming_plot

Create a real-time streaming chart that updates client-side with simulated data or replays a dataset progressively. Outputs a self-contained HTML page with no server required.

Instructions

Create a live-updating streaming visualization with simulated real-time data.

The output is a self-contained HTML page with Panel periodic callbacks that simulates streaming data — the chart updates in real time. This works entirely client-side, no server needed.

If a dataset is provided, the streaming simulation replays its data progressively. Otherwise, generates a random walk time series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoColumn for x-axis (uses index if not provided)
yNoColumn for y-axis (uses first numeric column if not provided)
titleNoPlot titleLive Streaming Data
n_pointsNoNumber of initial points (for generated data)
plot_typeNoChart type for streaming — 'line', 'scatter', 'area', 'step'line
window_sizeNoMax visible points in the rolling window
dataset_nameNoOptional dataset to stream from (replays rows progressively)
update_intervalNoMilliseconds between updates

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: output is self-contained HTML, uses Panel callbacks, client-side execution, data replay vs random walk. Could mention limitations like performance or suitability for large data.

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?

Three efficient paragraphs with no fluff. Every sentence adds value. Front-loaded with key purpose and output format.

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?

Covers main functionality: output type, client-side behavior, dataset handling. With 8 parameters and output schema, it is reasonably complete. Minor gaps: no mention of how to stop streaming or expected behavior with large datasets.

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 baseline is 3. The description adds context (e.g., dataset_name for replay, n_points for generated data) but does not significantly enhance individual parameter meaning beyond schema descriptions.

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 it creates a live-updating streaming visualization with simulated real-time data. It distinguishes from siblings like 'create_plot' (static) and 'create_datashader_plot' (for large data) by emphasizing real-time simulation and client-side execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied (real-time simulation, client-side, no server), but no explicit guidance on when to use this versus siblings like 'create_plot' or 'create_crossfilter'. No exclusions or alternatives mentioned.

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