Skip to main content
Glama
Grist MCP Server
by nic01asFr

Add Grist Records

add_grist_records

Adds one or more records to a specified table in a Grist document using document and table IDs, with each record defined by column-value pairs.

Instructions

Ajoute des enregistrements à une table Grist.

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": {
      "doc_id": "<doc_id>",
      "table_id": "<table_id>",
      "records": "<records>"
    },
    "name": "add_grist_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document Grist
recordsYesListe des enregistrements à ajouter. Chaque enregistrement est un dictionnaire où les clés sont les noms des colonnes et les valeurs sont les données. Exemple: [{"nom": "Dupont", "prénom": "Jean", "âge": 35}]
table_idYesL'ID de la table

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document Grist"
    • addedInput schema / properties / records / description
      Added value: +"Liste des enregistrements à ajouter. Chaque enregistrement est un dictionnaire\n    où les clés sont les noms des colonnes et les valeurs sont les données.\n    Exemple: [{\"nom\": \"Dupont\", \"prénom\": \"Jean\", \"âge\": 35}]"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID de la table"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it only restates the write intent. It says nothing about batch semantics, partial-failure behavior, whether unknown columns are rejected, or what happens on duplicate rows — all material for an append operation.

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

Conciseness4/5

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

A single efficient sentence with no filler, front-loading the action and resource. It is terse to the point of under-specification, but nothing written is wasted.

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?

For a three-parameter mutation tool with no annotations, this description is too thin; an agent gets no signal about side effects, the distinction from the safe variant, or error conditions. The output schema and full param coverage offset some of this, but the behavioral gap remains.

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 description coverage is 100%, and the schema itself explains doc_id, table_id, and even gives an example record shape for the records array. The description adds no meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Ajoute des enregistrements à une table Grist'), so an agent can tell it creates rows in a table. It does not, however, distinguish this from the sibling add_grist_records_safe, which appears to be a near-identical operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives; the presence of add_grist_records_safe is never addressed, nor are prerequisites such as permissions or whether the target table must already exist. The agent must infer everything from the name.

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