Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_submit_form

Submit a SmartSuite form in two steps: preview the required fields, then submit values keyed by field slug. Validates fields and creates a record.

Instructions

Submit a SmartSuite form — creates a record through the form's submission pipeline, exactly as a user filling out the form would. Two-step: call WITHOUT values to get the form's input spec (fields to collect, with type and choice hints); then call WITH values (keyed by field slug, using normal SmartSuite record value shapes) to submit. Validates that supplied fields are on the form and that required fields are present. Submitting requires readwrite or admin mode (it creates a record).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdYesThe form (report) ID — from smartsuite_list_forms
valuesNoField values keyed by slug (same shapes as record create). Omit to preview the form's fields first.
applicationIdYesThe application ID the form belongs to
Behavior5/5

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

Beyond annotations, the description fully discloses the two-step workflow, validation behavior (required fields, field membership), and the need for readwrite/admin mode. No annotation contradiction.

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 extremely concise, using two sentences to convey purpose, workflow, validation, and auth. Front-loaded with the primary action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers the process and constraints, it omits details about the return value shape for both steps (preview and submission). Given no output schema, this is a notable gap for an agent expecting a response.

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 already covers all parameters (100% coverage). The description adds value by integrating the parameters into the two-step process, explaining the role of 'values' omission for preview, and clarifying that values use slug keys and record shapes.

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 tool submits a SmartSuite form to create a record, exactly as a user filling out the form. It distinguishes from sibling tools like direct record creation by emphasizing the form pipeline.

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 explains the two-step usage pattern (call without values to preview, then with values to submit) and mentions authentication mode. However, it does not explicitly contrast with alternative tools like direct record creation or other form actions.

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