Skip to main content
Glama
purian

widgetdash-mcp

by purian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Push metrics to iPhone widget

push_metrics
Idempotent

Create or update a WidgetDash data source and set its title, icon, category, and full metrics list for iPhone widgets and Live Activities.

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/sort_order keep their current values. Requires WIDGETDASH_WRITE_KEY.

Input Schema

TableJSON 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 among sources on the widget (lower first). If omitted, keeps the existing order (default 0).
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. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (idempotent, non-destructive, open-world), but the description adds the critical behavioral fact that the metrics list REPLACES existing metrics, that omitted display fields are preserved, and that a write key is required. These are non-obvious traits not derivable from the 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?

Three dense sentences with no filler: identity and effect first, the replace-vs-merge caveat second, the alternative tool and auth requirement last. Nothing repeats the schema verbatim.

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 7-param upsert tool with nested objects and no output schema, the description covers purpose, merge behavior, auth, and sibling routing. It does not say what the call returns or whether a source_key response payload is produced, a minor gap given no output schema exists.

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 baseline is 3. The description goes slightly beyond by summarizing the field set (title, icon, category, metrics) and emphasizing the destructive replace semantics of the metrics array, which the schema only implies through item descriptions.

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?

States a specific verb pair (create or update) and resource (WidgetDash data source) with the concrete surface it affects (iPhone Home Screen / Lock Screen widgets and Live Activities). It also names the sibling it is not (push_number), so an agent can separate the two without opening schemas.

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?

Explicitly routes the agent: use push_number to change a single value, use this tool to set the full metrics list. It also states the merge semantics for omitted fields and the required WIDGETDASH_WRITE_KEY, which is exactly the when/how 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