Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Table

modify_table

Update a Grist table's properties by changing its ID within a document, with an optional new table ID.

Instructions

Modifie les propriétés 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>"
    },
    "name": "modify_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
table_idYesL'ID actuel de la table
new_table_idNoNouvel ID pour la table (optionnel)

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 / new_table_id / description
      Added value: +"Nouvel ID pour la table (optionnel)"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID actuel de la table"
  2. First observedv0.1.0

TDQS

C2.4/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 discloses almost nothing. It implies a mutation but does not state required permissions, whether a table rename breaks references elsewhere, or what collateral effects occur; only the existence of the output schema spares it the absolute floor.

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, front-loaded sentence with no waste and no redundancy. Brevity is not achieved at the cost of clutter, though the economy here reflects under-specification rather than tight writing.

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 zero annotations and three parameters, the description should explain what properties can change and what happens to existing references when the table ID changes. Given full schema coverage and an output schema, some burden is lifted, but the core mutation semantics remain unexplained.

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 new_table_id are already documented in the schema itself. The description adds no meaning beyond that — it never mentions that the operation is effectively a rename keyed on new_table_id — so the documented baseline of 3 applies.

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

Purpose2/5

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

"Modifie les propriétés d'une table" restates the tool name Modify Table and names only a resource, not which properties. The word "propriétés" is generic and never resolved to the one updatable field the schema actually exposes (new_table_id), so an agent cannot tell what this tool can change without opening 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 guidance on when to use this versus modify_column, create_table, or the various modify_document/modify_workspace siblings. The only implicit signal is that the target is a table, leaving all routing decisions to inference from the tool name.

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