Skip to main content
Glama
Grist MCP Server
by nic01asFr

Create Table

create_table

Adds a new table to a Grist document using a unique table ID, with optional column definitions to define its structure.

Instructions

Crée une nouvelle table dans un document.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
columnsNoListe des définitions de colonnes (optionnel) Exemple: [ {"id": "name", "type": "Text", "label": "Nom"}, {"id": "status", "type": "Choice", "choices": ["A", "B", "C"]}, {"id": "amount", "type": "Numeric", "description": "Montant en euros"} ]
table_idYesID de la nouvelle table (doit être unique dans le document)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / columns / description
      Added value: +"Liste des définitions de colonnes (optionnel)\n    Exemple: [\n        {\"id\": \"name\", \"type\": \"Text\", \"label\": \"Nom\"},\n        {\"id\": \"status\", \"type\": \"Choice\", \"choices\": [\"A\", \"B\", \"C\"]},\n        {\"id\": \"amount\", \"type\": \"Numeric\", \"description\": \"Montant en euros\"}\n    ]"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / table_id / description
      Added value: +"ID de la nouvelle table (doit être unique dans le document)"
  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 says the tool creates a table. It omits what permissions are required, whether the operation is reversible or how deletion works, what happens if table_id collides, and whether columns can be added later.

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?

It is a single clean sentence with no wasted words, and the key action is front-loaded. The terseness is efficient rather than padded, though it leaves no room for the context an agent would want.

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?

Because an output schema exists, return values need not be described, but for a mutation tool with zero annotations and three parameters, the description should still cover permissions, idempotency, and what is created. As written it gives the agent only the bare action statement, which is thin for a creation operation.

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%, including a worked example for the columns array and uniqueness guidance for table_id, so the schema already does the heavy lifting. The one-line description adds no meaning beyond the schema, which justifies the baseline 3.

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 ('Crée une nouvelle table') scoped to a document, which is clear enough for an agent to grasp the action. However, it offers no differentiation from nearby siblings such as create_schema, create_column, or modify_table, so the agent must infer the boundary itself.

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 (e.g. the document must exist), and no pointer to alternatives for adding columns or altering an existing table. The agent is left to infer usage 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.