SmartSuite MCP Server

smartsuite_describe_form

Read-only

Retrieve a SmartSuite form's full structure: settings, sharing, pages, bound fields, content elements, and conditional visibility.

Instructions

Get the full structure of a SmartSuite form for review: settings (title, description, submit label, redirect, branding, logo), sharing (enabled, public URL, password protection), and the page-by-page layout. Each page is an input (form), review, or submission page. Input-page items are parsed into bound fields (slug, label, required, help text) and content elements (heading, html_block/paragraph, callout, consent, divider, image, video, recaptcha, pdf_viewer), including section groupings and conditional-visibility flags.

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>",
      "formId": "<formId>"
    },
    "name": "smartsuite_describe_form"
  }
}

Input Schema

Name	Required	Description	Default
`formId`	Yes	The form (report) ID
`applicationId`	Yes	The application ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.8Jul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true; description adds rich detail about what is returned (settings, sharing, page layout with bound fields and content elements, conditional visibility). No contradictions. Provides significant context 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.

Conciseness4/5

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

Single sentence that front-loads purpose and then lists details. Is somewhat long but each element is relevant. Could be split into two sentences for readability, but overall efficient.

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?

No output schema exists, yet description fully covers return structure: top-level categories (settings, sharing, page layout) and nested elements (bound fields, content elements, conditional flags). Complete for a read tool with two parameters.

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

Parameters3/5

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

Schema coverage is 100% with basic descriptions of formId and applicationId. The description does not add additional semantic meaning for parameters; it focuses on output. Baseline 3 is appropriate.

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?

Clearly states 'Get the full structure of a SmartSuite form for review' and enumerates elements (settings, sharing, page-by-page layout). Distinguishes from sibling tools like smartsuite_list_forms, which likely returns only metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Implies usage for review/diagnostics by describing the output, but does not explicitly state when to use versus alternatives or provide exclusions. Siblings include mutations (create, update, submit) and listing, so context hints at read-only usage, but no direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server