Skip to main content
Glama
Sign In
SmartSuite MCP Server

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_normalize_dashboard_widgets

Fixes dashboard widgets with wrong sizes or overlaps by resetting them to natural sizes and re-stacking. Offers a dry-run preview before applying changes.

Instructions

Repair a dashboard's widgets: reset them to their natural per-type size and/or re-stack them to remove overlaps. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. Fixes dashboards built with wrong sizes (e.g. metric cards left too tall — which re-saving in the UI does not correct) or with widgets piled on top of each other (all near position (0,0), so they overlap and hide each other). Dry-run preview (before→after per widget) unless confirm:true. SIZE: by default HEIGHT is normalized; dimension:"both" also fixes width; restrict with widgetTypes (e.g. ["summary-card-widget"]). REFLOW: pass reflow:true to re-lay-out the tab — widgets sharing the same current row (same position_y) are kept side-by-side, and rows are stacked top-to-bottom by their tallest widget so nothing overlaps (reflow repositions ALL widgets on the tab, regardless of widgetTypes). Use tabId to limit to one tab.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dashboardId": "<dashboardId>"
    },
    "name": "smartsuite_normalize_dashboard_widgets"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoOptional: only affect widgets on this tab.
reflowNoRe-stack widgets top-to-bottom to remove overlaps (preserves each row's side-by-side columns). Default false.
confirmNoSet true to apply; otherwise returns a dry-run preview of the changes.
dimensionNo"height" (default) fixes height only; "both" also fixes width.
dashboardIdYesThe dashboard (report) ID.
widgetTypesNoOptional: only resize these widget types (e.g. ["summary-card-widget"]). Does not limit reflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4.8/5.0
Behavior5/5

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

Annotations indicate write operation (readOnlyHint=false). Description adds critical behavioral details: dry-run mode unless confirm:true, reflow behavior (keeps side-by-side, stacks rows), default normalization only height. Comprehensive disclosure beyond 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?

Dense but efficient. Front-loaded with main purpose, then prerequisites, use cases, and per-parameter details. Every sentence adds value; no fluff.

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?

For a 6-parameter tool with no output schema, description covers both modes (size and reflow), dry-run behavior, prerequisites, and parameter nuances. Complete enough for an agent to invoke correctly.

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

Parameters5/5

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

100% schema coverage, and description adds substantial context: dimension 'both' also fixes width, confirm toggles apply vs dry-run, widgetTypes limited to resize only. Each parameter's meaning is enriched well beyond 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?

Description specifies verb 'repair' with resource 'dashboard widgets' and clearly distinguishes two operations (size normalization and reflow). It differentiates from sibling tools like add/update/remove widget by addressing specific dashboard anomalies.

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?

Explicitly states required mode (readwrite/admin) and environment variable (SMARTSUITE_ENABLE_SCHEMA_WRITE=true). Describes when to use: for wrong sizes or overlapping widgets, noting that UI re-saving doesn't fix. Lacks explicit alternatives but context is clear.

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