Skip to main content
Glama
Sign In
SmartSuite MCP Server

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_update_records

Batch update multiple SmartSuite records with dry-run validation before writing. Requires readwrite or admin mode, and confirmation to apply changes.

Instructions

Batch update multiple records. Supports dry-run mode. Requires readwrite or admin mode.

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>",
      "records": "<records>"
    },
    "name": "smartsuite_update_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, validate only without writing (default true)
confirmNoMust be true to execute when dryRun is false
recordsYesList of records to update
applicationIdYesThe application ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint false, consistent with mutation. The description adds beyond annotations by disclosing dry-run support and permission requirements, but does not detail error handling or side effects.

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 concise sentences with no fluff. All information is front-loaded and relevant.

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

Completeness4/5

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

Covers purpose, basic usage, and constraints (permissions, dry-run). Lacks output information and error scenarios, but sufficient for a batch update tool with no output schema.

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 descriptions for all parameters. The description adds no parameter-level details beyond restating dry-run mode, so 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?

The description clearly states 'Batch update multiple records', specifying the verb ('update') and resource ('multiple records'). It distinguishes from siblings like smartsuite_update_record (singular) and smartsuite_create_records (create).

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?

The description mentions dry-run mode and required permissions ('readwrite or admin mode'), which provide context but does not explicitly state when to use this tool over alternatives like smartsuite_update_record.

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