Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Column

delete_column

Removes a specified column from a Grist table by document ID, table ID, and column ID.

Instructions

Supprime une colonne d'une table.

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": "delete_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
table_idYesL'ID de la table
column_idYesL'ID de la colonne à supprimer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / column_id / description
      Added value: +"L'ID de la colonne à supprimer"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • 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 supplied, so the description carries the full behavioral burden, yet it only restates the operation. It does not say whether deletion is permanent, what happens to data in that column, or whether dependent formulas/reference columns break — the key facts for a destructive mutation tool.

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 short sentence with the resource and operation front-loaded and no filler. It is efficient, though the brevity comes partly from omission of necessary context, and the French wording is inconsistent with the English tool name and title.

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 destructive three-parameter mutation with no annotations, the description should at minimum flag irreversibility and any cascade effects; it says nothing on either point. An output schema exists, so return values need not be explained, but the operational caveats are 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% and each of doc_id, table_id, column_id is documented in the schema itself, so the baseline of 3 applies. The description adds no ordering, ID-format, or lookup guidance beyond the schema.

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?

"Supprime une colonne d'une table" names a specific verb (delete) and resource (a column of a table), so an agent knows exactly the operation. It does not differentiate from siblings such as modify_column, which could plausibly also drop a column, so the sibling-routing value is absent.

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 or when-not-to-use guidance, no mention of prerequisites (owning the doc/table, column being unreferenced), and no pointer to modify_column as an alternative. An agent must infer the call context entirely from the name.

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