Skip to main content
Glama

origin_plot_chart_atlas

Create a plot by specifying your data file and chart intent; the tool routes to the appropriate chart type to visualize your data.

Instructions

Create a plot using chart-atlas intent routing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
intentYes
x_colNo
y_colsNo
z_colNo
y_error_colNo
x_error_colNo
book_nameNo
sheet_nameNo
excel_sheetNo
delimiterNo
encodingNo
headerNo
skiprowsNo
nrowsNo
na_valuesNo
graph_nameNo
titleNo
x_labelNo
y_labelNo
style_modeNonature
palette_roleNo
export_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description provides minimal behavioral insight beyond 'create a plot'. No disclosure of side effects, prerequisites, or error conditions.

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 too brief, omitting critical information. It is not a model of conciseness because it fails to provide necessary content.

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

Completeness1/5

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

Given 23 parameters and no schema descriptions, the description is severely incomplete. Output schema exists but does not compensate for the lack of explanation.

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%, and the description adds no parameter explanations. Many parameters (e.g., 'intent', 'style_mode') remain ambiguous.

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

Purpose3/5

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

The description states 'Create a plot' (verb+resource) but uses vague term 'chart-atlas intent routing' without explanation. It does not clearly distinguish from sibling plot tools like origin_plot_line or origin_chart_atlas_route.

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 the many sibling plot tools. The description does not mention any context or 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