Skip to main content
Glama
Grist MCP Server
by nic01asFr

Add Grist Records Safe

add_grist_records_safe

Add records to a Grist table only after validating that the table and columns exist, with correction suggestions if needed.

Instructions

Ajoute des enregistrements avec validation préalable de la structure.

Cette version sécurisée valide l'existence de la table et des colonnes avant d'ajouter les enregistrements, et suggère des corrections si nécessaire.

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_safe"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
recordsYesListe des enregistrements à ajouter
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 à ajouter"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID de la table"
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the pre-validation of table and column existence and that corrections are suggested, but says nothing about what happens to the batch if validation fails, whether any records are written, permission requirements, or atomicity.

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?

Two short sentences, front-loaded with the action and then the safety behavior. Slight redundancy in restating 'ajouter les enregistrements' in the second sentence, but no real waste.

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?

For a three-parameter batch-insert tool with a fully described schema and an existing output schema, the key differentiator (pre-validation with suggested corrections) is explained. The remaining gap is failure semantics on the write itself, which is less critical given the output schema exists.

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%, so doc_id, table_id, and records are already documented in the schema; the description adds no format, constraint, or batch-size detail. Baseline 3 is appropriate when the schema does the work.

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') and adds the defining trait of this variant: prior structural validation of table and columns. It implicitly distinguishes itself from the plain add_grist_records sibling via 'version sécurisée', though it never names that alternative.

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?

Usage is only implied: the mention of a 'version sécurisée' suggests choosing this over the unsafe variant when structure validation matters, but the description never explicitly says when to use this tool or when to prefer add_grist_records. No exclusions or prerequisites are given.

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