Skip to main content
Glama

origin_change_plot_data

Replace an existing plot in a graph with new X/Y data from a worksheet by removing the old plot and adding new data. Specify plot index, worksheet, and column indices.

Instructions

Replace a plot by removing it and adding new worksheet X/Y data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plot_indexYes
worksheetYes
x_colYes
y_colYes
graph_nameNo
layer_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions removal and addition (destructive actions) but fails to detail reversibility, authentication needs, or other side effects like impact on other plots or graph properties.

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

Conciseness2/5

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

The description is a single 12-word sentence, which is concise but underspecified for a tool with 6 parameters and a destructive operation. It lacks details that could be added without much verbosity.

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 having an output schema, the description does not mention it or the operation's outcome. It fails to explain parameters like plot_index and layer_index, leaving the tool's behavior incomplete for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all parameters. It only covers worksheet, x_col, and y_col (X/Y data), but omits plot_index, graph_name, and layer_index which are required or important. This leaves significant parameter ambiguity.

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 action ('Replace a plot') and specifies the mechanism ('removing it and adding new worksheet X/Y data'). It distinguishes this tool from siblings like origin_remove_plot_from_graph and origin_add_plot_to_graph by combining both operations.

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?

The description does not provide any guidance on when to use this tool versus alternatives, such as when to add a plot separately. No explicit context or exclusions are given, leaving the agent to infer usage.

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/Ge-Shun/origin-mcp'

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