Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Column

modify_column

Update a Grist column's label, formula, data type, description, visibility, or ID so table schemas stay accurate and adaptable.

Instructions

Modifie les propriétés d'une colonne.

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>",
      "column_id": "<column_id>"
    },
    "name": "modify_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoNouveau libellé d'affichage (optionnel)
doc_idYesL'ID du document
formulaNoNouvelle formule (optionnel, "" pour supprimer)
table_idYesL'ID de la table
column_idYesL'ID actuel de la colonne
column_typeNoNouveau type de données (optionnel)
descriptionNoNouvelle description (optionnel)
visible_colNoNouveau colRef pour les Ref (optionnel)
new_column_idNoNouvel ID pour la colonne (optionnel)
widget_optionsNoNouvelles options d'affichage (optionnel)
untie_col_id_from_labelNoDissocier l'ID du label (optionnel)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.2.2
    • addedInput schema / properties / column_id / description
      Added value: +"L'ID actuel de la colonne"
    • addedInput schema / properties / column_type / description
      Added value: +"Nouveau type de données (optionnel)"
    • addedInput schema / properties / description / description
      Added value: +"Nouvelle description (optionnel)"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / formula / description
      Added value: +"Nouvelle formule (optionnel, \"\" pour supprimer)"
    • addedInput schema / properties / label / description
      Added value: +"Nouveau libellé d'affichage (optionnel)"
    • addedInput schema / properties / new_column_id / description
      Added value: +"Nouvel ID pour la colonne (optionnel)"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID de la table"
    • addedInput schema / properties / untie_col_id_from_label / description
      Added value: +"Dissocier l'ID du label (optionnel)"
    • addedInput schema / properties / visible_col / description
      Added value: +"Nouveau colRef pour les Ref (optionnel)"
    • addedInput schema / properties / widget_options / description
      Added value: +"Nouvelles options d'affichage (optionnel)"
  2. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says properties are modified. It does not disclose permission requirements, whether renames break references, whether formula changes trigger recalculation, or whether the operation is reversible. The verb "Modifie" at least signals mutation, which is the only behavioral content present.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no wasted wording, but its brevity comes at the cost of under-specification rather than genuine conciseness. It is structurally clean yet substantively thin for an 11-parameter mutation tool.

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 mutation tool with 11 parameters and no annotations, the description is inadequate: it omits any warning about the risky operations exposed by the schema (changing column_type or new_column_id, clearing formulas with an empty string). An output schema exists, so return values need not be explained, but critical invocation context is missing.

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%, with all 11 parameters individually documented (label, formula, column_type, new_column_id, visible_col, widget_options, etc.), so the schema already does the semantic heavy lifting. The description adds nothing beyond it, which matches the baseline for high coverage.

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 clear verb and resource ("Modifie les propriétés d'une colonne"), so an agent knows this mutates an existing column rather than creating or deleting one. It does not distinguish itself from siblings like create_column or delete_column, and it does not say which properties are modifiable, leaving that to the schema.

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 explicit guidance on when to use this tool versus alternatives, and no prerequisites (such as needing an existing column ID from describe_document) are mentioned. Usage context is only implied by the tool name and the required identifiers.

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