Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Records

list_records

Retrieve records from a Grist table with optional sorting and result limits to control result order and size.

Instructions

Liste les enregistrements dans une table Grist avec tri et limitation optionnels.

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_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoColonne de tri (optionnel, format: "colonne" ou "colonne:asc/desc")
limitNoNombre maximum d'enregistrements à retourner (optionnel)
doc_idYesL'ID du document Grist
table_idYesL'ID de la table

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document Grist"
    • addedInput schema / properties / limit / description
      Added value: +"Nombre maximum d'enregistrements à retourner (optionnel)"
    • addedInput schema / properties / sort / description
      Added value: +"Colonne de tri (optionnel, format: \"colonne\" ou \"colonne:asc/desc\")"
    • 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 must carry the behavioral burden alone. It does not say whether the call returns all rows when limit is omitted, whether results are paginated, what permissions are required, or how large tables are handled — all material for an unbounded list operation.

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 efficient sentence with no filler, front-loading the core action before the optional modifiers. It is well sized for a simple list tool, though it leaves no room for the missing behavioral context.

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 explained, and the schema fully covers the four parameters. However, with no annotations and no statement about default/unbounded result size, the definition is only minimally sufficient for a read tool that could return large result sets.

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 the schema already documents doc_id, table_id, sort format, and limit. The description only echoes the existence of sort and limit without adding syntax or edge-case meaning, which matches the baseline for full schema coverage.

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 ("Liste les enregistrements dans une table Grist") and names the two optional modifiers, sort and limit. It does not distinguish this tool from the many sibling list_* tools, so the agent gets a clear purpose but no differentiation.

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 list_tables or describe_document, nor any prerequisite or exclusion. The only usage signal is that sort and limit are optional, which the schema already states.

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