Skip to main content
Glama
AiAgentKarl

mcp-interactive-ui-server

create_chart

Create interactive chart schemas for bar, line, pie, scatter, area, donut, and heatmap visualizations using structured data with labels, values, and optional colors.

Instructions

Generiert eine Chart-Definition (Bar, Line, Pie, Scatter, etc.).

Erstellt ein Chart-Schema mit Daten und Konfiguration, das MCP-Clients als interaktives Diagramm rendern können.

Unterstützte Chart-Typen: bar, line, pie, scatter, area, donut, heatmap.

Daten-Format:

  • Für bar/line/area: {"labels": ["Jan","Feb"], "datasets": [{"label": "Sales", "values": [10,20]}]}

  • Für pie/donut: {"labels": ["A","B","C"], "values": [30, 50, 20]}

  • Für scatter: {"datasets": [{"label": "Set 1", "points": [{"x": 1, "y": 2}]}]}

  • Für heatmap: {"x_labels": [...], "y_labels": [...], "values": [[...]]}

Args: chart_type: Art des Charts (bar, line, pie, scatter, area, donut, heatmap) data: Chart-Daten als Dictionary title: Chart-Titel x_label: Beschriftung X-Achse y_label: Beschriftung Y-Achse colors: Optionale Farbliste (hex oder CSS-Farbnamen) stacked: Gestapelte Darstellung (nur bar/area)

Returns: JSON-String mit dem Chart-Schema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chart_typeYes
dataYes
titleNoChart
x_labelNo
y_labelNo
colorsNo
stackedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description explains that the tool creates a chart schema and returns a JSON string, with no side effects or destructive actions mentioned. Without annotations, it adequately discloses the return format and data examples.

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 well-structured with sections for supported types, data formats, args, and returns. Slightly lengthy but each part is informative, earning its place.

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 an output schema exists (mentioned), the description provides sufficient context: chart types, data formats, and parameter details. No gaps remain for a typical usage scenario.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by listing all parameters, their meanings, and detailed data format examples for each chart type. This adds essential meaning beyond the bare schema.

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 a chart definition with specific types (bar, line, pie, etc.) and provides data format examples. It distinguishes from sibling tools like create_dashboard or create_form, which serve different purposes.

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

Usage Guidelines3/5

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

The description implies the tool is for creating chart definitions but does not explicitly provide when-to-use or when-not-to-use guidance. No alternative tools are mentioned for comparison, though sibling names suggest distinct purposes.

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/AiAgentKarl/mcp-interactive-ui-server'

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