Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_describe_application

Read-only

Retrieve a SmartSuite application's schema: field slugs, types, choice options, and record term. Use before creating or updating records to know valid field values.

Instructions

Describe a SmartSuite application schema, including field slugs, types, and options, plus the record term (custom record terminology). Always call this before creating or updating records so you know field slugs and valid values. Set includeLayout:true to also return the record-view layout (sections with collapse flags, and the field row arrangement of the active layout mode). TOKEN COST: the schema is large; a full table is ~1k+ tokens. The schema is STABLE within a session — call this once per table and reuse the result; do NOT re-describe the same application (use forceRefresh only after you change the schema). When you only need field slugs/types/choices (e.g. to build or query records), use verbosity:"compact" or the lighter smartsuite_list_fields instead of the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verbosityNoField detail level. "compact" = slug/label/type + choice options + linked-app only (cheapest; use for surveys, CSV/data work, or when scanning many tables). "standard" (default) also adds help text and flags when set. "full" adds the raw params blob (large — only when you need every setting).
forceRefreshNoBypass cache and fetch fresh schema. Only needed after the schema changed this session — otherwise redundant.
applicationIdYesThe application ID
includeFieldsNoInclude field definitions (default true)
includeLayoutNoInclude the record-view layout: { mode, sections (with collapsed flags), rows, hiddenFields }. Default false.
Behavior5/5

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

Beyond readOnlyHint annotation, description details token cost (~1k+ tokens), schema stability within session, and caching advice. No contradiction with annotations.

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?

Two paragraphs, front-loaded with key purpose. Every sentence adds value—token cost, caching, verbosity levels, and usage guidance—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?

Despite no output schema, description covers return values, token cost, caching, parameter options, and usage context. Completely adequate for a read-only schema introspection tool with 5 parameters.

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%, baseline 3. Description adds meaningful context for parameters, e.g., explaining includeLayout returns 'sections with collapse flags' and forceRefresh is 'only needed after schema changed'. Justifies higher score.

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?

Specific verb 'Describe' with clear resource: 'SmartSuite application schema, including field slugs, types, and options, plus the record term.' Distinguishes from siblings like smartsuite_list_fields (lighter) and smartsuite_describe_field (per-field).

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?

Explicitly states 'Always call this before creating or updating records' and provides alternatives: 'use verbosity:"compact" or the lighter smartsuite_list_fields'. Also advises caching: 'call this once per table and reuse'.

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