Skip to main content
Glama
Grist MCP Server
by nic01asFr

Get Table Schema

get_table_schema

Retrieves detailed schema information for a specified Grist table to inspect its columns, types, and structure before querying or modifying records.

Instructions

Obtient le schéma détaillé d'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": "get_table_schema"
  }
}

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

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. The verb 'obtient' makes it clear this is a non-mutating read, and 'détaillé' hints at completeness, but nothing is said about permissions, whether the document must exist or be loaded, or failure behavior.

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 front-loaded and no wasted wording. It is appropriately sized, though its brevity comes at the cost of detail rather than from efficiency.

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?

An output schema exists, so return values need not be described. However, for a schema-inspection tool with no annotations, the definition says nothing about what 'detailed' covers (columns, types, constraints) or how it relates to sibling inspection tools, leaving the agent with only the bare purpose.

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 both required parameters (doc_id and table_id) documented in the input schema. The description adds no further meaning about these identifiers, so the baseline of 3 applies.

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 gives a specific verb and resource: retrieving the detailed schema of a Grist table. An agent can tell this is a schema-inspection read, but it does not distinguish the tool from siblings such as export_schema, describe_document, or validate_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 export_schema, describe_document, or validate_schema. The usage context is only implied by the phrase 'schéma détaillé d'une table'.

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