Skip to main content
Glama
Grist MCP Server
by nic01asFr

Create Workspace

create_workspace

Creates a new workspace inside an existing Grist organization, letting you set the workspace name and parent organization ID to organize documents under a dedicated space.

Instructions

Crée un nouvel espace de travail dans une organisation.

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": {
      "org_id": "<org_id>",
      "name": "<name>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNom du nouvel espace de travail
org_idYesL'ID de l'organisation

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 nouvel espace de travail"
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation"
  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 behavioral burden. It implies a mutation but says nothing about required permissions, whether the workspace name must be unique within the org, side effects, or whether the newly created workspace is returned.

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 front-loaded sentence with no redundant wording. It is efficient, though its brevity reflects under-specification rather than tight editing.

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

Completeness2/5

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

For a mutation tool with zero annotations, the definition is too thin: it omits permission requirements, name-uniqueness behavior, and any note on what the call returns. The presence of an output schema covers return values, but the pre-call behavioral context an agent needs is missing.

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 coverage is 100%, so both parameters (name, org_id) are already documented in the input schema. The phrase 'dans une organisation' loosely reinforces the org_id parameter but adds no format, constraint, or validation detail 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 nouvel espace de travail dans une organisation'), which is enough to distinguish a create operation from siblings like delete_workspace or modify_workspace by name. It stops short of any explicit sibling differentiation, so it is clear but not fully disambiguating.

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 create a workspace versus modifying an existing one, and no mention of prerequisites such as org membership or admin rights. The agent must infer usage entirely from the tool name and the phrase 'dans une organisation'.

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