Skip to main content
Glama
Sign In
SmartSuite MCP Server

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_list_deleted_fields

Read-only

List soft-deleted fields in a SmartSuite solution to find their slugs, labels, and types before restoring them.

Instructions

List soft-deleted fields in a solution (read-only). Returns each deleted field's slug, label, and fieldType. Solution-scoped — the API does not attribute deleted fields to their source application, so results are not app-filtered. Restore one with smartsuite_restore_field (supplying the applicationId it belonged to).

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": {
      "solutionId": "<solutionId>"
    },
    "name": "smartsuite_list_deleted_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
solutionIdYesThe solution ID whose deleted fields to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds that the API does not attribute deleted fields to their source application (so no app filtering), and that it returns slug, label, and fieldType. This provides useful behavioral context beyond the annotation. No contradictions.

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?

Three sentences, each conveying essential information. The first sentence states purpose and read-only nature. The second specifies return fields. The third adds scope limitation and a pointer to restore tool. No unnecessary words.

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?

Given the tool has only one parameter and no output schema, the description covers all essential aspects: what it does, what it returns, its scope, a limitation, and a related action. It is fully informative for an agent to use correctly.

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% for the single parameter solutionId, with a clear description. The description does not add any additional parameter details beyond the schema, so it meets the baseline but does not exceed it.

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 that the tool lists soft-deleted fields, is read-only, and returns specific data. It distinguishes from active field listing tools (smartsuite_list_fields) by focusing on deleted fields and mentioning solution-scoping. The verb 'List' with resource 'soft-deleted fields' is specific.

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 provides context for when to use this tool: to see deleted fields. It mentions that results are not filtered by app, which sets expectations. It also suggests the next step of restoring with smartsuite_restore_field. However, it does not explicitly exclude other alternatives beyond the scope limitation.

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