Skip to main content
Glama

origin_plot_chart_atlas

Create a plot from a data file by specifying an intent and customize axes, labels, and style for publication-ready graphs.

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_modeNoorigin_default
palette_roleNo
palette_nameNo
export_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description does not disclose any behavioral traits such as whether it modifies data, requires specific permissions, or has any side effects. With no annotations, the description carries the full burden, but it only says 'Create a plot'.

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

Conciseness3/5

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

The description is concise at one sentence, but it lacks necessary structure and detail. It is too sparse for a complex tool.

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 the tool's complexity (24 parameters, many sibling tools) and no annotations, the description is severely incomplete. It does not provide enough context for an AI agent to select or invoke the tool correctly.

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

Parameters1/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 meaning to the 24 parameters. It does not explain required fields 'path' and 'intent' or any other parameter.

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 the tool creates a plot using chart-atlas intent routing, but 'chart-atlas intent routing' is undefined jargon. It gives a vague sense of purpose without distinguishing from sibling plot tools like origin_plot or origin_plot_auto.

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 vs alternatives. No exclusions or context about when it is appropriate.

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