Skip to main content
Glama
Sign In
SmartSuite MCP Server

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_create_dashboard

Create a dashboard in a SmartSuite app with a unique label and optional tabs; preview changes first unless confirmed.

Instructions

Create a dashboard in an application. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. Supply applicationId and a unique label (checked; suggests an alternative if taken). Optionally pass tabs (array of tab names, or {name, order} objects) — otherwise one default tab is created. Add widgets afterward with smartsuite_add_dashboard_widget. Dry-run preview unless confirm:true.

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": {
      "applicationId": "<applicationId>",
      "label": "<label>"
    },
    "name": "smartsuite_create_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabsNoOptional tab names (strings) or {name, order} objects. Default: one tab named "Tab".
labelYesDashboard name (unique within the application).
confirmNoSet true to create; otherwise returns a dry-run preview.
descriptionNoOptional description.
applicationIdYesThe application ID the dashboard belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4.7/5.0
Behavior5/5

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

The description openly discloses key behaviors: dry-run capability (unless confirm:true), label uniqueness check (with alternative suggestion), and the requirement for readwrite/admin mode and the environment variable. These details go beyond the annotations (readOnlyHint: false) and provide actionable transparency.

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 concise (3-4 sentences) and well-structured: it starts with the primary purpose, followed by prerequisites, behavior notes, and a sibling reference. Every sentence adds value without redundancy.

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 creation tool with no output schema, the description adequately covers inputs, behavior (dry-run, uniqueness), and outcome (creation or preview). It also provides a logical next step (adding widgets). No missing critical information is apparent.

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?

While the input schema covers all 5 parameters with descriptions, the description adds meaningful semantics: it explains the dual type for tabs (strings or objects) and the default tab behavior, clarifies the confirm parameter's dry-run effect, and emphasizes label uniqueness checks. This enhances understanding 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 the action ('Create a dashboard in an application'), specifies the resource ('dashboard') and context ('in an application'), and differentiates from sibling tools like smartsuite_add_dashboard_widget by noting it is used afterward.

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?

The description provides clear context for when to use the tool (creating a dashboard) and prerequisites (readwrite/admin mode and environment variable). It also guides the agent on post-creation steps (use smartsuite_add_dashboard_widget). However, it does not explicitly state when not to use it or compare with similar creation tools.

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