SeaTable MCP

Official

Overview Schema Source Related Servers Discussions Admin

get_row

Read-onlyIdempotent

Retrieve a single row by its unique ID from a specified table in your SeaTable base, enabling direct access to specific records for reading, updating, or processing.

Instructions

Get a row by ID from a table

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>",
      "row_id": "<row_id>"
    },
    "name": "get_row"
  }
}

Input Schema

Name	Required	Description	Default
`table`	Yes	Target table name
`row_id`	Yes	Row ID (the _id field)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.2Apr 23, 2026

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, destructiveHint=false, idempotentHint=true. The description does not contradict these. It adds the context that this tool retrieves a row, which is consistent. No extra behavioral details are needed beyond what annotations provide.

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?

The description is a single, clear sentence that completely conveys the tool's purpose without extraneous words. It is front-loaded with the verb and resource.

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's simplicity (2 params, no output schema), the description covers the core purpose. It could optionally note that the row includes all fields or reference the schema for return format, but it is adequate for a basic getter.

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%, so baseline is 3. The description does not add parameter meaning beyond what the schema already provides (table name and row_id). No additional explanation of formats or constraints is given.

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 uses the specific verb 'Get' and resource 'row by ID from a table', clearly identifying the operation and resource. It effectively distinguishes this tool from siblings like 'find_rows', 'list_rows', and 'get_row_activities', which serve different purposes.

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 implies usage for fetching a single row by ID, which is intuitive. However, it does not explicitly state when not to use this tool (e.g., for batch operations use 'list_rows' or 'find_rows'), though the sibling context helps disambiguate.

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