Skip to main content
Glama
Grist MCP Server
by nic01asFr

Update Grist Records

update_grist_records

Updates existing records in a specified Grist table using a document ID, table ID, and record IDs with changed fields.

Instructions

Met à jour des enregistrements existants dans 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": "update_grist_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
recordsYesListe des enregistrements à mettre à jour. Chaque enregistrement doit contenir un champ 'id' Exemple: [{"id": 1, "nom": "Dupont", "prénom": "Jean"}]
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"
    • addedInput schema / properties / records / description
      Added value: +"Liste des enregistrements à mettre à jour. \n    Chaque enregistrement doit contenir un champ 'id'\n    Exemple: [{\"id\": 1, \"nom\": \"Dupont\", \"prénom\": \"Jean\"}]"
    • 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 burden of behavioral disclosure, and it delivers almost none. It does not say whether updates are partial merges or full replacements, what happens to omitted fields, what permissions are required, or whether the operation is reversible. For a mutation tool with zero annotation coverage, this is a significant gap.

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 wasted wording and the operation front-loaded. The brevity is a virtue structurally, though it reflects under-specification rather than disciplined conciseness.

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

Completeness3/5

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

The complete schema descriptions and an output schema reduce the descriptive burden, which keeps this at a minimum-viable level. However, for a mutation tool with no annotations, the description never states update semantics (merge vs. replace) or failure conditions, which are exactly what an agent needs before invoking it.

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%, and the schema already documents doc_id, table_id, and records, including an example showing that each record must carry an 'id'. The description adds nothing beyond that, so the baseline 3 applies, though the schema does the heavy lifting here.

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 names a specific verb and resource: updating existing records in a Grist table. That's enough for an agent to know what it does and that it targets existing (not new) records. It stops short of explicitly distinguishing the tool from add_grist_records, add_grist_records_safe, or delete_grist_records, so it isn't a 5.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives for creating or deleting records. The only implicit signal is the word 'existants', which hints that records must already exist, but the agent is left to infer this.

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