Skip to main content
Glama
Sign In
widgetdash-mcp

widgetdash-mcp

by purian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Push metrics to iPhone widget

push_metrics
Idempotent

Create or update a widget data source with title, icon, category, and complete metrics list, replacing existing metrics so iPhone Home, Lock Screen, and Live Activity widgets show current values.

Instructions

Create or update a WidgetDash data source shown on the user's iPhone Home Screen / Lock Screen widgets and Live Activities. Sets the source's title, SF Symbol icon, category and its full list of metrics (label + value + type + color). The metrics list REPLACES the source's current metrics; use push_number to change a single value. Omitted display_name/icon/category keep their current values; sort_order only applies when the source is created. Requires WIDGETDASH_WRITE_KEY.

Input Schema

NameRequiredDescriptionDefault
iconNoSF Symbol name shown next to the title, e.g. 'dollarsign.circle.fill', 'chart.bar.fill', 'server.rack', 'heart.fill', 'cart.fill'. If omitted, keeps the existing icon (default 'circle.fill').
metricsYesMetrics to show, in display order. Small widgets show the first few, so put the most important first.
categoryNoFree-form grouping, e.g. 'finance', 'monitoring', 'fitness'. If omitted, keeps the existing category (default 'general').
raw_dataNoOptional arbitrary JSON object stored alongside the metrics (not shown on the widget). If omitted, existing raw_data is kept.
sort_orderNoPosition for a NEW source among your sources (lower first, default 0). Ignored when updating an existing source: its order is set in the WidgetDash app.
source_keyYesStable identifier for this data source, e.g. 'stripe_mrr' or 'server_health'. Lowercase letters, digits, '_' or '-'. Pushing to an existing key updates it; a new key creates a new widget source.
display_nameNoTitle shown on the widget, e.g. 'Stripe'. If omitted, keeps the existing name (or derives one from source_key for new sources).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • changedInput schema / properties / metrics / items / properties / type / description
      Previous value: -"How the widget renders the value: 'number' = big bold figure (counts, money, KPIs); 'text' = plain short string; 'status' = colored badge (e.g. 'Healthy', 'Down'); 'progress' = bar, value must be 0-100; 'percentage' = compact percent text. If omitted: 'number' for numeric-looking values (42, $12,400, 3.5%), otherwise 'text'."New value: +"How the widget renders the value: 'number' = big bold figure (counts, money, KPIs); 'text' = plain short string; 'status' = colored badge (e.g. 'Healthy', 'Down'); 'progress' = bar, value must be 0-100; 'percentage' = compact percent text; 'timestamp' = a moment shown as live relative time (e.g. '8 hours ago'), value is ISO 8601 like 2026-10-23T05:00:00Z or Unix epoch seconds. If omitted: 'number' for numeric-looking values (42, $12,400, 3.5%), otherwise 'text'."
    • changedInput schema / properties / metrics / items / properties / type / enum
      Previous value: -[
-  "number",
-  "text",
-  "status",
-  "progress",
-  "percentage"
-]New value: +[
+  "number",
+  "text",
+  "status",
+  "progress",
+  "percentage",
+  "timestamp"
+]
    • changedInput schema / properties / metrics / items / properties / value / description
      Previous value: -"The value to display, pre-formatted as you want it shown (e.g. '$12,400', '42', 'Healthy'). For 'progress' use 0-100."New value: +"The value to display, pre-formatted as you want it shown (e.g. '$12,400', '42', 'Healthy'). For 'progress' use 0-100; for 'timestamp' an ISO 8601 time or Unix epoch seconds."
    • addedInput schema / properties / metrics / items / properties / wide
      Added value: +{
+  "description": "Optional. true gives the metric a full-width row of its own on Large widgets (iOS app 1.8+), for long text such as a title. Other text that shares a row shows up to two lines. Put wide metrics last to keep the others in one row.",
+  "type": "boolean"
+}
    • changedInput schema / properties / sort_order / description
      Previous value: -"Position among sources on the widget (lower first). If omitted, keeps the existing order (default 0)."New value: +"Position for a NEW source among your sources (lower first, default 0). Ignored when updating an existing source: its order is set in the WidgetDash app."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior1/5

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

Annotations declare destructiveHint=false, but the description says the metrics list REPLACES the source's current metrics. Replacing a full list overwrites/removes prior metrics, which is a destructive update, so the description contradicts the annotation. Otherwise the description adds useful context such as the write key and create-only sort_order, but the contradiction forces a 1 under the rules.

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?

The description is four tight sentences and front-loads the create-or-update behavior plus the replacement warning. Every sentence adds either routing guidance, overwrite semantics, or authentication requirements. There is no filler.

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?

With rich schema descriptions and annotations, the description covers the key behavioral details: mutation, full-list replacement, omitted-field preservation, create-only sort_order, and auth. It does not describe the response or error behavior, which is a minor gap for a mutating tool with no output schema.

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 description coverage is 100%, so the schema already documents parameters in detail. The description still adds meaning by emphasizing that metrics REPLACES the existing list, omitted display fields are preserved, and sort_order is create-only. It does not add much granular syntax beyond the schema, but the replacement semantics are important.

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 states a specific verb and resource: create or update a WidgetDash data source shown in iPhone widgets and Live Activities. It also distinguishes the tool from push_number by explaining that this tool sets the full metrics list. An agent can identify the operation without opening the schema.

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 says to use push_number to change a single value, which routes the agent between this tool and its closest sibling. It also explains that omitted display_name/icon/category keep current values and that sort_order only applies on creation. The WIDGETDASH_WRITE_KEY requirement is stated.

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