Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Workspace

delete_workspace

Deletes a Grist workspace by workspace ID, removing it when the workspace is no longer needed.

Instructions

Supprime 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": "delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesL'ID de l'espace de travail à supprimer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail à supprimer"
  2. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/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, and it discloses nothing. For a destructive, irreversible operation it omits whether deletion cascades to documents, columns, and access rules, whether it can be undone, what permissions are required, and whether confirmation is needed.

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?

One short sentence with no filler, so nothing is wasted, but the brevity reflects under-specification rather than economy of expression. It is adequately front-loaded but carries almost no information.

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?

An output schema exists, so return values need not be explained, but for a destructive single-parameter tool with zero annotations the description should at minimum flag irreversibility and side effects. It provides none of that, leaving an agent unable to judge risk.

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?

There is only one parameter (workspace_id) and schema description coverage is 100%, with the schema already saying it is the ID of the workspace to delete. Per the baseline rule for high coverage, a 3 is appropriate; the description adds nothing beyond the schema but nothing is missing either.

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

Purpose2/5

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

"Supprime un espace de travail" merely restates the tool name and title (delete_workspace / Delete Workspace) in French. It gives no scope, no distinction from siblings like delete_organization or delete_document, and no indication of what deleting a workspace entails.

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 modify_workspace, delete_organization, or describe_workspace first. No prerequisites, no preconditions, and no warnings are stated.

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