Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Columns

list_columns

Lists all columns in a specified Grist table using document and table IDs, helping you inspect table structure before querying or managing records.

Instructions

Liste toutes les colonnes dans une table Grist.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
table_idYesL'ID de la table

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • 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 disclosure burden. 'Liste' implies a read-only enumeration, but nothing is said about permissions required, whether hidden/private columns are included, ordering, or truncation/pagination behavior for large tables. With zero annotation coverage and no added behavioral context, this is a significant gap.

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?

A single short sentence with no wasted words, which is appropriately sized for a simple two-parameter read tool. However, the brevity borders on under-specification rather than disciplined conciseness, since nothing beyond the bare action is conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two required string parameters), the input schema is fully documented, and an output schema exists that covers the return shape, so the description need not explain results. Even so, for a tool with no annotations it should say at least that the call is a non-destructive read and note any access requirements; that omission leaves it only minimally complete.

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% (both doc_id and table_id are documented as 'L'ID du document' and 'L'ID de la table'), so the baseline of 3 applies. The description's 'dans une table' loosely ties the call to the table parameter but adds no 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?

States a concrete verb and resource: 'Liste toutes les colonnes' scoped to 'une table Grist'. An agent immediately knows it returns column metadata for a given table, and it is distinguishable from list_records or list_tables by the resource named. It does not explicitly name a sibling to defer to, but the purpose is unambiguous.

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 guidance, no mention of prerequisites (that doc_id and table_id must already be known, e.g. from list_tables), and no comparison with alternatives such as describe_document or create_column. Usage must be inferred entirely from the name and required parameters.

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