SeaTable MCP

Official

Overview Schema Source Related Servers Discussions Admin

add_select_options

Idempotent

Add new options to a single-select or multi-select column in a SeaTable table. Use this before writing rows that contain option values not yet defined in the column.

Instructions

Add new options to a single-select or multi-select column. Use this before writing rows with option values that do not exist yet.

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": {
      "table": "<table>",
      "column": "<column>",
      "options": "<options>"
    },
    "name": "add_select_options"
  }
}

Input Schema

Name	Required	Description
`table`	Yes	Target table name
`column`	Yes	Name of the single-select or multi-select column
`options`	Yes	Array of options to add

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.2Apr 23, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate idempotentHint: true and destructiveHint: false, which the description does not contradict. The description adds the behavioral context that this should be used proactively before row writes, which is helpful. No info about atomicity or error behavior is provided, but the annotations cover the main safety concerns.

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 that front-load the core action and follow with usage guidance. No wasted words.

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?

Given the tool has no output schema and three well-documented parameters, the description covers the essential purpose and usage context. It is complete enough for an agent to decide when to use this tool, though it could briefly mention that multiple options can be added in one call.

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 has 100% description coverage, so the description does not need to add much for parameters. However, it provides no additional meaning beyond the schema fields. Baseline score of 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 the tool adds new options to a single-select or multi-select column. It specifies the resource (column options) and the action (add), and distinguishes from siblings like add_row and append_rows which operate on rows, not column options.

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 explicitly advises to use this tool before writing rows with option values that do not exist yet, providing context for when to use it. However, it does not mention when NOT to use it or any alternatives, though the sibling list does offer other add operations for different purposes.

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