Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Tables

list_tables

Retrieves all tables in a specified Grist document using its document ID, so you can inspect available tables before querying or managing records.

Instructions

Liste toutes les tables dans un document 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>"
    },
    "name": "list_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du 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 provided, so the description carries the full disclosure burden, yet it says nothing about the operation being a safe read, what happens with an invalid or inaccessible doc_id, or the scope/ordering of returned rows. With an output schema present the return shape needn't be explained, but the safety and error profile remain undisclosed.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though at the cost of omitting any qualifying information.

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?

For a simple one-parameter enumeration tool with a fully documented parameter and an output schema, the description is minimally sufficient. It still leaves the read-only nature and failure behavior unstated, which is a gap but not a blocking one.

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?

The single parameter doc_id has 100% schema description coverage ('L'ID du document'), so the schema already carries the meaning. The description adds only the implication that the document is the container being enumerated, which is baseline-level value.

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 ('Liste toutes les tables') and scopes the result to a single Grist document. It clearly differs from siblings like list_records or list_columns by naming 'tables', though it does not explicitly contrast itself with them.

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 tool versus alternatives such as describe_document, list_columns or list_records, and no stated prerequisites. The agent must infer usage purely from the name and resource noun.

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