Skip to main content
Glama
KyuRish

mcp-dashboards

by KyuRish
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

Sparkline Cards

render_sparkline_chart
Read-onlyIdempotent

Render sparkline card grids to compare trends and current values for multiple metrics in one view.

Instructions

Standalone sparkline card grid. Prefer using KPI cards with sparkline[] inside render_dashboard instead for a cleaner integrated look.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesArray of sparkline card items
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
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 / data / items / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / data / items / properties / value / 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

A4/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, so the safety profile is covered. The description adds no further behavioral context such as what the render returns, whether it is persisted, or how it behaves with large data arrays, so it only meets the reduced bar.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, and the scoping/steering message is front-loaded right after the one-line purpose. Nothing could be removed without losing information.

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

Completeness4/5

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

For a 6-parameter render tool with fully documented schema and no output schema, the description gives enough to make the routing decision correctly. It is slightly thin on what a standalone card grid render actually returns, but that gap is minor given the consistent render_* family pattern.

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 100%, so the schema already documents title, data, theme, palette, effects and typography in detail. The description contributes no additional meaning about any parameter, which is the expected baseline 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?

The description names a specific resource ('sparkline card grid') and marks its scope as 'standalone', which is what separates it from the broader dashboard renderers. It stops short of an explicit verb, but an agent can tell exactly what artifact this produces versus siblings like render_line_chart or render_dashboard.

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

Usage Guidelines5/5

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

It explicitly routes the agent away from this tool: prefer KPI cards with sparkline[] inside render_dashboard for an integrated look. That names both the alternative tool and the condition under which it wins, which is exactly the when/when-not guidance an agent needs.

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