Skip to main content
Glama
KyuRish

mcp-dashboards

by KyuRish
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Scatter Chart

render_scatter_chart
Read-onlyIdempotent

Render an interactive scatter plot from x/y coordinate data with multiple series, optional lines, annotations, and themes for correlation and trend analysis.

Instructions

Render an interactive scatter plot with x/y coordinate data. Supports multiple series and optional connecting lines. 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
effectsNoOverride effects: none, subtle, shimmer, neon, energetic
optionsNo
paletteNoOverride palette only (mix-and-match)
datasetsYesOne or more data series with {x, y} points
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the output is an interactive scatter plot and supports multiple series, connecting lines, and themes, but does not disclose return format, file-saving behavior, or other operational details beyond what the schema and annotations provide.

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 three sentences, front-loaded with the core purpose, and avoid unnecessary verbosity. The third sentence about themes is somewhat redundant with the schema but still concise overall.

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

Completeness3/5

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

Given 7 parameters, nested objects, 40+ sibling render tools, and no output schema, the description covers the core purpose and capabilities but omits usage differentiation and return behavior. The rich schema and safety annotations carry much of the burden, leaving this as minimum viable.

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 high at 86%, so the schema already documents parameters thoroughly. The description mentions x/y data, multiple series, optional connecting lines, and themes, but these map directly to schema fields (datasets, showLine, theme) without adding syntax, format, or default information beyond the schema.

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?

The description states a specific verb and resource ('Render an interactive scatter plot') with x/y coordinate data, multiple series, and optional connecting lines. It is clearly distinct from most siblings by naming scatter plot, but it does not explicitly differentiate from adjacent chart types like render_line_chart or render_bubble_map.

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?

There is no guidance on when to choose this tool over alternatives such as render_line_chart or render_bubble_map, nor any exclusions or prerequisites. The description only restates capability without context for selection.

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