Skip to main content
Glama
KyuRish

mcp-dashboards

by KyuRish
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Line Chart

render_line_chart
Read-onlyIdempotent

Create interactive line or area charts to visualize trends over time or categories. Add multiple series, smooth curves, gradient fills, and theme styling.

Instructions

Render an interactive line or area chart. Supports smooth curves, gradient fill, and multiple series. Supports themes for styled visuals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeNoTheme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot, office-red
titleYesChart title
labelsYesX-axis labels (e.g. dates, categories)
effectsNoOverride effects: none, subtle, shimmer, neon, energetic
optionsNo
paletteNoOverride palette only (mix-and-match)
datasetsYesOne or more data series
typographyNoOverride typography: professional, luxury, cyberpunk, editorial, mono, bold, system, techno

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.1
    • changedInput schema / properties / options / properties / annotations / items / oneOf
      Previous value: -[
-  {
-    "properties": {
-      "axis": {
-        "description": "Which axis the line is on",
-        "enum": [
-          "x",
-          "y"
-        ],
-        "type": "string"
-      },
-      "color": {
-        "description": "Line color",
-        "type": "string"
-      },
-      "label": {
-        "description": "Label text",
-        "type": "string"
-      },
-      "style": {
-        "description": "Line style. Default: dashed",
-        "enum": [
-          "solid",
-          "dashed"
-        ],
-        "type": "string"
-      },
-      "type": {
-        "const": "line",
-        "type": "string"
-      },
-      "value": {
-        "description": "Position on the axis",
-        "type": "number"
-      }
-    },
-    "required": [
-      "type",
-      "axis",
-      "value"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "color": {
-        "description": "Background color",
-        "type": "string"
-      },
-      "label": {
-        "type": "string"
-      },
-      "type": {
-        "const": "box",
-        "type": "string"
-      },
-      "xMax": {
-        "type": "number"
-      },
-      "xMin": {
-        "type": "number"
-      },
-      "yMax": {
-        "type": "number"
-      },
-      "yMin": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "color": {
-        "type": "string"
-      },
-      "content": {
-        "description": "Label text",
-        "type": "string"
-      },
-      "type": {
-        "const": "label",
-        "type": "string"
-      },
-      "x": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "string"
-          }
-        ],
-        "description": "X position (number or category label)"
-      },
-      "y": {
-        "description": "Y position",
-        "type": "number"
-      }
-    },
-    "required": [
-      "type",
-      "x",
-      "y",
-      "content"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "axis": {
+        "description": "Which axis the line is on",
+        "enum": [
+          "x",
+          "y"
+        ],
+        "type": "string"
+      },
+      "color": {
+        "description": "Line color",
+        "type": "string"
+      },
+      "label": {
+        "description": "Label text",
+        "type": "string"
+      },
+      "style": {
+        "description": "Line style. Default: dashed",
+        "enum": [
+          "solid",
+          "dashed"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "const": "line",
+        "type": "string"
+      },
+      "value": {
+        "description": "Position on the axis",
+        "type": "number"
+      }
+    },
+    "required": [
+      "type",
+      "axis",
+      "value"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "color": {
+        "description": "Background color",
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "type": {
+        "const": "box",
+        "type": "string"
+      },
+      "xMax": {
+        "type": "number"
+      },
+      "xMin": {
+        "type": "number"
+      },
+      "yMax": {
+        "type": "number"
+      },
+      "yMin": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "type"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "color": {
+        "type": "string"
+      },
+      "content": {
+        "description": "Label text",
+        "type": "string"
+      },
+      "type": {
+        "const": "label",
+        "type": "string"
+      },
+      "x": {
+        "description": "X position (number or category label)",
+        "type": [
+          "number",
+          "string"
+        ]
+      },
+      "y": {
+        "description": "Y position",
+        "type": "number"
+      }
+    },
+    "required": [
+      "type",
+      "x",
+      "y",
+      "content"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changedv2.2.0
    • changedInput schema / properties / theme / description
      Previous value: -"Theme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot"New value: +"Theme preset: boardroom, corporate, sales-floor, golden-treasury, clinical, startup, ops-control, tokyo-midnight, zen-garden, consultant, black-tron, black-elegance, black-matrix, forest-amber, forest-earth, sky-light, sky-ocean, sky-twilight, gray-hf, gray-copilot, office-red"
  3. Addedv2.1.0
  4. Removedv1.0.1
  5. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds useful capability context (interactive output, smooth curves, gradient fill, multi-series, theming), but says nothing about output format, persistence, or interaction model.

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?

Three short sentences, front-loaded with the core action, no filler. It is efficient, though the third sentence about themes partially duplicates the second's capability listing.

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?

With 88% schema coverage and full annotation coverage, the description need not explain parameters or safety. For a nested, 8-parameter render tool with no output schema, the remaining needs – recognizing a chart render – are met; the noted gaps (return value, sibling routing) are minor given how much the schema already carries.

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 88%, so the schema already documents nearly all 8 parameters in detail. The description's mentions of smooth curves, gradient fill, multiple series, and themes loosely map to options.smooth, options.fill, datasets, and theme, but adds no syntax, defaults, or constraints beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

States a specific verb+resource ('Render an interactive line or area chart') and lists distinguishing capabilities. However it does not explicitly differentiate itself from siblings like render_bar_chart or render_scatter_chart, and the 'line or area' phrasing leaves the chart type slightly ambiguous.

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 choose this over ~25 sibling render_* tools, and no prerequisites or exclusions. The reader must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools