Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

smartsuite_create_application

Create a new table in a SmartSuite solution and provision all its fields inline, avoiding slow post-creation field additions. Requires the solutionId, table name, and optional field definitions.

Instructions

Create a new table (application) in a solution. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. Supply a name and the solutionId. The table is created with a default "Title" primary field and a record term ("what each record is called", default "Record") — the record term is always set explicitly so it is never left empty (an empty record term can break list-view/grid widget creation against the table). PASS fields TO CREATE THE TABLE AND ALL ITS FIELDS IN ONE REQUEST: an array of { fieldType, label, params? } entries (same shape as smartsuite_create_field). This is the ONLY true bulk field path SmartSuite offers and it is dramatically faster than adding fields afterwards — one request for all of them, versus ~1s per field via smartsuite_create_fields against an existing table. So when a table is new, always create its fields here. SmartSuite also adds its own default field set (Title, Description, Assigned To, Status, Due Date, Priority, …) alongside yours. Dry-run preview unless confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe table name.
fieldsNoOptional: fields to provision inline with the table, in order — all in this single request. Each entry: { fieldType, label, params? }, same semantics as smartsuite_create_field. aiPrompt is not supported here (the fields it would reference do not exist yet); set AI prompts after the table exists.
confirmNoSet true to create; otherwise returns a dry-run preview.
recordTermNoWhat each record is called (singular), e.g. "Request". Defaults to "Record".
solutionIdYesThe solution to create the table in.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Optional: fields to provision inline with the table, in order — all in this single request. Each entry: { fieldType, label, params? }, same semantics as smartsuite_create_field. aiPrompt is not supported here (the fields it would reference do not exist yet); set AI prompts after the table exists.",
+  "items": {
+    "properties": {
+      "fieldType": {
+        "description": "SmartSuite field type, e.g. textfield, numberfield, singleselectfield, linkedrecordfield.",
+        "type": "string"
+      },
+      "label": {
+        "description": "Field display label.",
+        "type": "string"
+      },
+      "params": {
+        "description": "Optional sparse field params; omit to accept type defaults.",
+        "type": "object"
+      }
+    },
+    "required": [
+      "fieldType",
+      "label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / recordTerm
      Added value: +{
+  "description": "What each record is called (singular), e.g. \"Request\". Defaults to \"Record\".",
+  "type": "string"
+}
  2. First observedv0.9.8

TDQS

A5/5.0
Behavior5/5

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

Beyond the minimal annotation (readOnlyHint: false), the description discloses several important behaviors: SmartSuite adds a default field set, a default Title primary field is created, recordTerm is set explicitly to avoid broken list/grid widgets, and the call is a dry-run unless confirm:true. This significantly exceeds what annotations alone convey.

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 long but densely informative; every sentence contributes either a requirement, an alternative, a side effect, or a rationale. The core action and prerequisites are front-loaded, and the key instructions about using fields inline and the dry-run behavior are clearly emphasized.

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 complex creation tool with no output schema and sparse annotations, the description covers the essential operational details: required permissions, side effects on the table, the bulk field path, the default field set, the recordTerm risk, and the confirm gate. An agent can invoke this tool correctly without needing additional context.

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?

Even though schema coverage is 100%, the description adds meaningful parameter context: fields reuse the smartsuite_create_field shape, aiPrompt is unsupported at table creation, recordTerm is described with the widget-breaking pitfall, and confirm's dry-run semantics are reinforced. This goes beyond the schema 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?

The description opens with a specific verb and resource: "Create a new table (application) in a solution." It clarifies that 'application' means table and distinguishes this from field-creation tools by naming smartsuite_create_field and smartsuite_create_fields as alternatives for existing tables.

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 states requirements (readwrite/admin mode and SMARTSUITE_ENABLE_SCHEMA_WRITE=true), when to use this tool (when a table is new), and when to use alternatives (adding fields afterwards via smartsuite_create_fields). It also explains the dry-run behavior and confirm flag, leaving no ambiguity about invocation.

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/SmartSuiteFoundry/smartsuite-mcp-server'

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