Skip to main content
Glama
ghostiee-11

holoviz-viz-mcp

by ghostiee-11

undo_plot

Revert the most recent change made to a plot, restoring it to its previous state.

Instructions

Undo the last modification to a plot. Returns the previous version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plot_idYesID of the plot to undo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral transparency. It only mentions returning the previous version but does not disclose critical behaviors like whether the operation is reversible, what happens with no undo history, or if it is destructive. The description is minimal and lacks important context.

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?

The description is extremely concise with two short sentences, no redundant phrases, and all information is front-loaded. Every word serves a purpose.

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

Completeness3/5

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

For a simple tool with one parameter and an output schema, the description is adequate but incomplete. It mentions returning the previous version but does not specify the return format, whether multiple undos are possible, or error handling. The presence of an output schema partially mitigates this, but the description still lacks completeness.

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 one parameter (plot_id) described as 'ID of the plot to undo'. The description adds no additional meaning beyond the schema, meeting the baseline. No extra details like format or constraints are provided.

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 undoes the last modification to a plot and returns the previous version. It uses a specific verb 'Undo' and resource 'last modification to a plot', effectively distinguishing it from siblings like modify_plot or clone_plot.

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?

The description implies usage for reverting the last plot modification but provides no explicit guidance on when to use this tool versus alternatives, such as using modify_plot for incremental changes. It lacks when-not-to-use or alternative recommendations.

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