SeaTable MCP

Official

Overview Schema Source Related Servers Discussions Admin

create_snapshot

Create a snapshot of the current SeaTable base to preserve its state. Requires at least one change and 10 minutes since the last snapshot.

Instructions

Create a snapshot of the current base. Requires at least one change since the last snapshot and at least 10 minutes since the last snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.2Apr 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations are all false, so the description carries the full burden. It discloses that the tool is not read-only (since it creates something), not destructive (snapshot creation is typically safe), and not idempotent (due to time-based restrictions). However, it does not mention what happens if conditions are not met (e.g., error message), which would be helpful.

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 sentences, efficient and front-loaded. Every sentence adds value: first states action, second states conditions.

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?

For a tool with no parameters, no output schema, and simple preconditions, the description is mostly complete. It could mention what the output is (e.g., snapshot ID or confirmation) but the lack of output schema reduces the need. Slightly incomplete for a new agent.

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

Parameters5/5

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

Input schema has no parameters, schema description coverage is 100%, so no additional parameter info is needed. The description adds value by explaining the prerequisites beyond what the schema provides.

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 the action 'Create a snapshot' and the resource 'the current base'. Differentiates from siblings like 'add_row' or 'delete_rows' by specifying it is about creating a snapshot, which is a distinct operation.

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 prerequisites: requires at least one change since last snapshot and at least 10 minutes since last snapshot. This helps the agent know when to use it and when not to.

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