Skip to main content
Glama
KyuRish

mcp-dashboards

by KyuRish
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Data Table

render_table
Read-onlyIdempotent

Render interactive, sortable data tables with clickable column headers and theme presets for styled visuals.

Instructions

Render a sortable, interactive data table. Click column headers to sort. Supports themes for styled visuals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYesArray of row objects. Keys must match column names.
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
titleYesTable title
columnsYesColumn names in display order
effectsNoOverride effects: none, subtle, shimmer, neon, energetic
optionsNo
paletteNoOverride palette only (mix-and-match)
typographyNoOverride typography: professional, luxury, cyberpunk, editorial, mono, bold, system, techno

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.1
    • removedInput schema / properties / rows / items / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / rows / items / additionalProperties / type
      Added value: +[
+  "string",
+  "number"
+]
  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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds that the output is interactive and themeable, but says nothing about what is produced or returned (an image, HTML, a saved file) or how it interacts with siblings like save_file.

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, front-loaded sentences with no filler. The middle sentence ('Click column headers to sort') describes end-user UI interaction and is of limited value to an invoking agent, but it is brief.

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?

With 8 parameters including nested objects, no output schema, and many sibling tools, the description should clarify what the tool produces and how it relates to file-saving or catalog tools. It leaves the return value and the reason to pick a table over a chart or dashboard unexplained.

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 (88%), so the schema documents title, columns, rows, theme, effects, options, palette and typography on its own. The description only adds that themes are supported for 'styled visuals', which is a minor gloss over what the schema already states.

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 a sortable, interactive data table'), which cleanly separates it from the chart-rendering siblings (pie, bar, line, etc.). It does not explicitly name an alternative, but the table-vs-chart distinction is self-evident.

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 the many sibling renderers (render_from_json, render_dashboard, or any chart tool), nor on prerequisites. The only clue is the resource type itself.

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