Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Organization

delete_organization

Deletes a specified Grist organization using its org_id to remove obsolete or unwanted organizations from your account.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
org_idYesL'ID de l'organisation à supprimer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.3/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, and it discloses nothing: not whether deletion is permanent or recoverable, whether it cascades to documents/workspaces, what authorization is required, or whether confirmation is expected. Only the bare implication of 'supprime' is conveyed.

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?

The single sentence is front-loaded and free of padding, but its brevity stems from under-specification rather than discipline. Nothing in it is wasteful, yet nothing earns its place beyond the tool name.

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 this is an unannotated destructive operation with irreversible consequences and the description says nothing about permanence, cascade effects, or required permissions. For a deletion tool that is a substantial omission.

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?

The single parameter org_id is fully documented in the schema itself (100% coverage), including its accepted integer-or-string form. The description adds no meaning beyond that, so the baseline of 3 applies.

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 une organisation" restates the tool name and title almost verbatim, adding only the verb 'delete' in French. It gives no scope, no distinction from destructive siblings such as delete_workspace or delete_document, and an agent gains nothing it did not already know from the identifier.

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 when-to-use guidance, no prerequisite or permission context, and no mention of alternatives (e.g. modify_organization or describe_organization). The agent must infer entirely from the tool name that this is the destructive path.

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