Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_create_formula_field

Validate and create a formula field in a SmartSuite application. Preview the result with a dry run first, then set confirm to true to append it to the table.

Instructions

Create a new formula field in a SmartSuite application. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. The expression is validated first — an invalid formula is never created — and a local lint pass reports the semantic traps SmartSuite's validator accepts (see smartsuite_validate_formula); those warnings are advisory and never block. Without confirm:true returns a dry-run preview (validation result + what would be created); set confirm:true to create. The field slug is generated automatically and the field is appended to the end of the table (SmartSuite ignores field positioning on create — use smartsuite_move_layout_field to rearrange).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesDisplay label for the new field
confirmNoMust be true to actually create. Omit/false for a validate-only dry run.
formulaYesThe formula expression
returnTypeNoOutput field type (default textfield). One of: textfield, numberfield, datefield, currencyfield, percentfield, singleselectfield, statusfield, yesnofield, emailfield, phonefield, durationfield, timefield, daterangefield, duedatefield.
applicationIdYesThe application ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • removedInput schema / properties / afterFieldSlug
      Removed value: -{
-  "description": "Optional: place the new field immediately after this existing field slug (defaults to last field).",
-  "type": "string"
-}
  2. First observedv0.9.8

TDQS

A4.6/5.0
Behavior5/5

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

With only readOnlyHint=false in annotations, the description carries strong behavioral context: required auth mode plus env flag, validation-before-create (invalid formulas never created), advisory lint warnings that never block, and the confirm-driven dry-run vs. real-create distinction. It also discloses side effects (auto-generated slug, field appended to end because positioning is ignored).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the verb and resource followed by prerequisites, then behavior, which is well-ordered. The remaining text is dense and information-bearing rather than padded, though the long multi-clause final sentences slightly reduce readability.

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 mutation tool with no output schema, the description covers everything an agent needs: auth requirements, validation guarantee, dry-run default, side effects on slug and ordering, and the sibling for repositioning. Nothing material is missing.

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 coverage is 100%, so the schema already documents all five parameters; baseline would be 3. The description adds real meaning for confirm by explaining the dry-run preview content and the create trigger, exceeding the schema's terse 'Must be true to actually create' text.

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 (Create), resource (new formula field), and scope (in a SmartSuite application), which cleanly separates it from siblings like smartsuite_create_field and smartsuite_update_formula_field. An agent can identify the tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names prerequisites (readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true) and routes to related siblings (smartsuite_validate_formula for lint detail, smartsuite_move_layout_field for repositioning). It does not state when to prefer this over the generic smartsuite_create_field, so it falls just short of full when/when-not guidance.

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