Skip to main content
Glama

origin_plot_auto

Inspect data columns and automatically select a suitable chart type, then create a plot. Optionally, describe your intent in natural language to guide chart selection.

Instructions

Inspect table columns, select a suitable chart route, and create the plot.

Provide intent when the desired comparison or relationship is known. Otherwise the router uses column types, cardinality, and selected X/Y/Z or error columns. Use origin_recommend_chart first when no graph should be created yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a CSV, TSV, TXT, DAT, XLS, or XLSX file.
nrowsNoMaximum number of data rows to read.
titleNoOptional graph page long name.
x_colNoColumn name or zero-based index to use as X. Defaults to the first column.
z_colNoOptional Z column for contour/XYZ plots.
headerNoZero-based row number to use as column names.
intentNoOptional natural-language chart intent used to guide automatic routing.
y_colsNoColumn names or zero-based indexes to plot as Y. Defaults to all non-X columns.
x_labelNoOptional X axis title.
y_labelNoOptional Y axis title.
encodingNoOptional text file encoding.
skiprowsNoRows to skip while reading.
book_nameNoOptional Origin workbook name.
delimiterNoDelimiter for text files. If omitted, CSV/TSV defaults or auto-detection are used.
na_valuesNoAdditional missing value markers.
graph_nameNoOptional Origin graph page name.
sheet_nameNoOptional Origin worksheet name.
style_modeNoGraph styling policy. origin_default/template/theme/none preserve Origin template defaults; nature applies origin-mcp styling after plotting.origin_default
excel_sheetNoExcel sheet name or zero-based index. Ignored for text files.
export_pathNoOptional graph export path.
x_error_colNoOptional X error column.
y_error_colNoOptional Y error column.
palette_nameNoOptional registered color palette name used by the selected style mode.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that the tool inspects columns, selects chart route, creates plot, and uses intent or column properties. However, it does not mention potential side effects (e.g., modifying workbook), permissions, or failure cases. Adequate but not detailed.

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?

Four sentences, front-loaded with purpose, then usage guidance. No unnecessary words. Efficient and well-structured.

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?

For a complex tool with 23 parameters and output schema present, the description covers core behavior and usage. It lacks details on error handling or return values, but output schema likely covers that. Good overall 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 description coverage is 100%. The description adds marginal value: explains intent role and default for y_cols. Baseline 3 is appropriate since schema already documents parameters well.

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 'Inspect table columns, select a suitable chart route, and create the plot.' It names specific verb+resource (inspect, select, create) and distinguishes sibling tool origin_recommend_chart by advising to use it first when no graph should be created.

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

Usage Guidelines5/5

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

Explicit guidance: 'Use origin_recommend_chart first when no graph should be created yet.' Also explains when to provide intent parameter and how the router works. Provides clear context for using this tool vs. alternatives.

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