Skip to main content
Glama
CariotInc

Cariot MCP Server

Official
by CariotInc

Generate Chart.js Configuration / Chart.js設定データ生成

generate_chart_config

Generates a Chart.js configuration object for bar, line, pie, doughnut, radar, or polarArea charts from provided labels and datasets.

Instructions

Generates Chart.js configuration data based on input data. Supports bar, line, pie, doughnut, radar, and polarArea chart types. Returns a ChartConfiguration object that can be used directly with Chart.js. IMPORTANT: When using this tool, you MUST embed the EXACT generated ChartConfiguration object in your final response WITHOUT any code block markers (no json, javascript, or any other formatting). Output the raw JSON object directly so the client can parse and use it. / 入力データに基づいてChart.js設定データを生成します。bar、line、pie、doughnut、radar、polarAreaのグラフタイプをサポートします。Chart.jsで直接使用できるChartConfigurationオブジェクトを返します。重要:このツールを使用した場合、生成されたChartConfigurationオブジェクトを、コードブロックマーカー(json、javascript等)を一切付けずに、そのまま生のJSONオブジェクトとして返答の末尾に含めてください。クライアントがパースして使用できるようにしてください。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartTypeYesChart type (bar, line, pie, doughnut, radar, polarArea) / グラフタイプ(bar、line、pie、doughnut、radar、polarArea)
labelsYesArray of labels for the chart / グラフのラベル配列
datasetsYesArray of datasets / データセット配列
titleNoChart title / グラフのタイトル
xAxisLabelNoX-axis label (for bar, line, radar charts) / X軸ラベル(bar、line、radarグラフ用)
yAxisLabelNoY-axis label (for bar, line, radar charts) / Y軸ラベル(bar、line、radarグラフ用)
Behavior3/5

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

No annotations are provided, so the description must carry behavioral info. It discloses the output format requirement but does not mention safety (e.g., read-only nature, error handling). The formatting instruction adds value beyond defaults.

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?

The description is bilingual and contains a critical usage instruction highlighted with 'IMPORTANT'. One sentence could be trimmed, but it remains focused and front-loaded.

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

Completeness5/5

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

Given the tool generates a configuration object and has no output schema, the description sufficiently explains the return type and usage. Parameters are well-documented in schema, and supported types are listed.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds the list of supported chart types, matching the chartType enum, but does not significantly enhance understanding of individual parameters.

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?

The description clearly states the tool generates Chart.js configuration from input data and lists supported chart types. It is distinct from retrieval-focused sibling tools like get_daily_report.

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

Usage Guidelines4/5

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

The description includes an explicit requirement to output the configuration without code block markers, guiding correct usage. It lacks explicit when-to-use vs alternatives, but siblings are all data retrieval, so context is clear.

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/CariotInc/cariot-mcp-server'

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