Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Workspace

modify_workspace

Update a Grist workspace's name using its workspace ID to keep workspace labels accurate and organized.

Instructions

Modifie les propriétés d'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": "modify_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNouveau nom pour l'espace de travail (optionnel)
workspace_idYesL'ID de l'espace de travail à modifier

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: +"Nouveau nom pour l'espace de travail (optionnel)"
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail à modifier"
  2. First observedv0.1.0

TDQS

C2.5/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 burden. "Modifie" implies a mutation, but it says nothing about required permissions, reversibility, what happens when name is null, or whether unspecified properties are left untouched — significant gaps for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so nothing is wasted. But the brevity comes from under-specification rather than disciplined writing, and the French description sits awkwardly against the English schema and siblings.

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?

The tool is simple (two parameters, one required) and an output schema exists, so return values need no explanation. Still, for a mutation tool with zero annotation coverage, the definition omits permission requirements and behavioral consequences that an agent needs before invoking it.

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, and the description adds no format or constraint details beyond that. The baseline of 3 applies; the plural "propriétés" is slightly at odds with a single modifiable field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence gives a verb ("Modifie") and a resource ("espace de travail"), so the basic operation is identifiable. However, "les propriétés" is vague — it never names the one actual mutable field (name) — and nothing distinguishes it from the sibling modify_workspace_access, which an agent could easily confuse it with.

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 at all on when to use this tool versus alternatives such as modify_workspace_access or delete_workspace, nor any stated prerequisites or permissions. The agent must infer usage purely from the tool name.

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