Skip to main content
Glama

origin_set_plot_style

Modify line, color, symbol, and transparency settings for a specific plot or all plots in a graph.

Instructions

Set line, color, symbol, and transparency style on one or all plots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
graph_nameNo
plot_indexNo
colorNo
line_widthNo
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 provided. Description only states it sets styles and mentions scope ('one or all plots'), but does not disclose side effects like overwriting, redrawing, or default behaviors. For a mutation tool with no annotations, more behavioral context is needed.

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?

Single sentence that efficiently conveys the purpose and scope. Front-loaded with core action. Could be expanded with more detail without losing 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?

Given 8 optional parameters and no schema descriptions, the description is incomplete. It does not explain how graph_name/plot_index target specific plots or the role of each parameter. Lacks differentiation from many sibling styling tools.

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 has 8 parameters with 0% description coverage. Tool description lists parameter categories (line, color, symbol, transparency) but does not explain formats, valid values (e.g., integer meaning for line_style), or the color array vs string distinction. The description adds minimal value beyond parameter names.

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?

Description clearly states the tool sets line, color, symbol, and transparency style on one or all plots. It is specific about the verb (set) and resource (plot style), and differentiates from sibling tools like origin_change_plot_data or origin_format_graph.

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. Does not mention prerequisites (e.g., a plot must exist) or when not to use it. Implies usage only through the purpose.

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