Skip to main content
Glama
Grist MCP Server
by nic01asFr

Create Document

create_document

Creates a new document in a specified Grist workspace by providing the workspace ID and document name.

Instructions

Crée un nouveau document dans un espace de travail.

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": {
      "workspace_id": "<workspace_id>",
      "name": "<name>"
    },
    "name": "create_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNom du nouveau document
workspace_idYesL'ID de l'espace de travail

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / name / description
      Added value: +"Nom du nouveau document"
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail"
  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 behavioral disclosure burden. It says a document is created in a workspace but does not mention permissions, whether names must be unique, whether an existing document with the same name conflicts, or what state the created document starts in.

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?

The description is a single efficient sentence with no wasted wording and the core action front-loaded. It is appropriately sized, though brevity comes at the cost of behavioral detail.

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?

With only two required parameters and complete schema coverage plus an output schema, the essential call mechanics are covered. However, for a creation/mutation tool with no annotations, the description should say more about permissions, uniqueness constraints, and initial document state.

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 both parameters are already documented in the schema. The description adds only the high-level context that the document belongs to a workspace, which marginally reinforces workspace_id but does not add syntax or format details 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?

The description states a specific verb and resource: 'Crée un nouveau document dans un espace de travail.' An agent can tell this creates a document rather than a workspace, table, or column, though it does not explicitly distinguish itself from sibling tools like modify_document or describe_document.

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, nor any prerequisites or exclusions. The description only states what it does, leaving the agent to infer that this is the right tool for creating a document.

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