Skip to main content
Glama

Manage Records

grist_manage_records
Destructive

Manage records in Grist documents with CRUD operations including add, update, delete, and upsert. Execute batched operations sequentially to handle cross-table dependencies using natural data formats.

Instructions

CRUD for records: add, update, delete, upsert. Batched operations execute sequentially for cross-table dependencies. Use natural formats (no "L" prefi

Example: {"docId":"abc123","operations":[{"action":"add","tableId":"Contacts","records":[{"Name":"Alice","Email":"alice@example.com"}]}]}

Use grist_help({tools:["grist_manage_records"]}) for full schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docIdYes
operationsYes
response_formatNo
Behavior3/5

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

Annotations already indicate destructive behavior (destructiveHint=true). The description adds that operations are sequential, but lacks details on what gets destroyed or auth requirements. Marginal added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but cut off mid-sentence, making it incomplete. Front-loading is good, but the truncation harms clarity and professionalism.

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

Completeness2/5

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

Given the tool's complexity (CRUD with batched operations), the description is insufficient. It lacks return value info, error handling, and limitations. The cut-off sentence leaves ambiguity about formats.

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

Parameters2/5

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

Schema coverage is 0%, so description must compensate. It provides an example but does not explain each parameter's meaning or format. The cut-off sentence ('no L prefix') is incomplete, and 'response_format' is undocumented.

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 performs CRUD operations on records (add, update, delete, upsert). It distinguishes from sibling tools like grist_get_records (read-only) and grist_manage_schema (schema management).

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 'batched operations execute sequentially for cross-table dependencies' but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. The example helps but guidelines are implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gwhthompson/grist-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server