Skip to main content
Glama

origin_set_plot_style

Set line style, color, symbol kind and size, bar gap, and transparency on plots to customize their visual appearance.

Instructions

Set line, color, symbol, column/bar gap, and transparency style on plots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
graph_nameNo
layer_indexNo
plot_indexNo
colorNo
line_widthNo
bar_gapNo
line_styleNo
symbol_kindNo
symbol_sizeNo
transparencyNo

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, and the description only states the action without disclosing behavioral traits. It fails to mention whether this is a mutating operation, any side effects, or required permissions. For a tool modifying plot state, this lack of transparency is a significant gap.

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

Conciseness4/5

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

A single sentence of 12 words, efficiently stating the tool's purpose with no unnecessary fluff. It is front-loaded, but could include a bit more context without harming conciseness.

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?

With 10 parameters, 0% schema coverage, no annotations, and an output schema, the description is insufficient. It omits that graph_name, layer_index, and plot_index are needed to target a specific plot, and provides no details on return value or preconditions. This leaves the agent with significant ambiguity.

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 description coverage is 0%, yet the description only lists parameter categories without adding meaningful semantics beyond parameter names. It does not explain valid values, formats (e.g., color as RGB array or string), or constraints, leaving the agent without crucial usage information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool sets line, color, symbol, column/bar gap, and transparency styles on plots, using a specific verb and listing relevant style aspects. It distinguishes from sibling tools like origin_plot (creation) and origin_set_axis (axis settings), though not exhaustively.

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 origin_set_plot_property or origin_format_graph. The description does not mention prerequisites, such as requiring an existing plot, nor does it provide criteria for choosing among similar styling 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/wxxuan2000-gif/origin-mcp-kimi'

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