Skip to main content
Glama

Hero Metric

render_hero_metric
Read-onlyIdempotent

Render interactive hero metrics to convey key insights: value and trend, progress, status, comparisons, rankings, countdowns, thresholds, breakdowns, satisfaction scores, and premium indicators.

Instructions

Render a purpose-driven hero metric widget. Pick the variant that answers your question:

  • big_number: 'How much? Which direction?' Default hero metric - clean, professional, works in any context. Large value + trend arrow + optional sparkline. Params: value, unit, change, changePeriod, sparkline[]

  • progress_ring: 'How close to goal?' Animated ring or half-gauge. Params: value, unit, label, progress (0-100), style ('ring'|'gauge'), size, color

  • status: 'Good or bad?' Pulsing dot + subsystem badges. Params: label, statusLevel ('good'|'warn'|'bad'), subsystems[{name,status}], count, peak

  • comparison: 'How do we compare?' Before/after + improvement. Params: before, after, improvement, beforeLabel, afterLabel

  • rank: 'Where do I stand?' Badge + percentile. Params: rank, total, percentile, rankChange

  • countdown: 'How long left?' Time segment boxes. Params: segments[{value,label}] OR deadline (ISO date)

  • threshold: 'Above or below limit?' Gradient bar + marker. Params: value, max, threshold, unit, zones[{label,from,to,color}]

  • breakdown: 'What is the split?' Stacked bar + legend. Params: items[{label,value,color?}]

  • nps: 'How satisfied?' Score + rating scale. Params: value, max (default 100), rating ('good'|'neutral'|'bad')

  • orb: 'What is the headline?' Dramatic glowing sphere. Use golden orb for resumes/portfolios. For tech meetings use only black, white, or crystal-colored orbs as subtle flair. Best with dark themes (tokyo-midnight, ops-control, startup). Avoid for formal contexts (boardroom, clinical, consultant). Params: value, unit, label, color

  • gem: 'Premium gem metric' Faceted/spherical gem - for wealth, fintech, trading, crypto, luxury contexts ONLY. Best with golden-treasury, tokyo-midnight themes. Do NOT use for corporate, clinical, consultant, or boardroom dashboards - use big_number instead. Params: value, unit, label, gemType. gemTypes: crystal='Future' (forecasts, projections) | black_pearl='Rare find' (alt investments, crypto) | golden_pearl='Treasure' (gold, commodities) | white_pearl='Clean total' (savings) diamond='Crown number' (net worth, total revenue) | ruby='What's critical' (urgent, burn rate) | sapphire='Foundation' (stability, uptime) | emerald='Growth' (YoY, appreciation)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoMaximum value for threshold/nps
peakNoPeak count
rankNoCurrent rank
sizeNoSize: sm/md/lg/xl
unitNoUnit label (e.g. 'grams', '%', 'USD')
afterNoAfter value
colorNoOverride accent color (hex)
countNoLive count
itemsNoBreakdown items
labelNoSub-label
styleNoprogress_ring style
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
totalNoTotal in ranking
valueNoMain metric value
zonesNoColor zones
beforeNoBefore value
changeNoPercentage change
ratingNoNPS rating override
effectsNoOverride effects: none, subtle, shimmer, neon, energetic
gemTypeNoGem type for variant=gem: diamond, ruby, sapphire, emerald, golden_pearl, white_pearl, black_pearl, crystal
paletteNoOverride palette only (mix-and-match)
variantNoWidget variant (default: big_number)
deadlineNoISO deadline date
progressNoRing fill 0-100
segmentsNoTime segments
sparklineNoMini bar sparkline data
thresholdNoThreshold limit line
afterLabelNoAfter column label
percentileNoPercentile
rankChangeNoPositions moved
subsystemsNoSubsystem badges
typographyNoOverride typography: professional, luxury, cyberpunk, editorial, mono, bold, system, techno
beforeLabelNoBefore column label
improvementNoImprovement label
statusLevelNoStatus level
changePeriodNoPeriod label for change (e.g. 'vs last month')
Behavior5/5

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

Adds rich behavioral context beyond annotations: 'animated ring', 'pulsing dot', 'glowing sphere', gem type meanings, and theme/context usage rules. No contradiction with annotations.

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?

Well-structured with clear variant headings and bullet points. Every sentence is informative, no fluff, appropriate length for the complexity.

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?

Thoroughly covers all 37 parameters across 11 variants, including usage guidance, behavioral traits, theme contexts, and gem type meanings. No output schema but description compensates fully.

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

Parameters4/5

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

Schema coverage is 100%, but description groups parameters per variant and explains their purpose (e.g., 'Large value + trend arrow + optional sparkline'), adding semantic value beyond the 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 it renders 'purpose-driven hero metric widgets', then lists 11 specific variants each with a distinct question they answer, distinguishing from sibling chart tools.

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

Usage Guidelines4/5

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

Provides explicit when-to-use guidance for each variant via questions (e.g., 'How much?', 'How close to goal?') and context restrictions (e.g., orb dark theme, gem luxury only). Lacks explicit exclusion of the tool itself versus siblings.

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/KyuRish/mcp-dashboards'

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