Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Workspace Access

modify_workspace_access

Change or remove a user's access to a Grist workspace by setting the workspace ID, user email, and access level (owners, editors, viewers, or null).

Instructions

Modifie l'accès d'un utilisateur à 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>",
      "user_email": "<user_email>",
      "access_level": "<access_level>"
    },
    "name": "modify_workspace_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_emailYesEmail de l'utilisateur
access_levelYesNiveau d'accès (owners, editors, viewers, ou null pour supprimer)
workspace_idYesL'ID de l'espace de travail

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / access_level / description
      Added value: +"Niveau d'accès (owners, editors, viewers, ou null pour supprimer)"
    • addedInput schema / properties / user_email / description
      Added value: +"Email de l'utilisateur"
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail"
  2. First observedv0.1.0

TDQS

C2.8/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 entire behavioral burden and delivers almost nothing beyond 'modifies access'. It does not say that changes are mutation/irreversible, what permissions are required, what happens to a user who has no existing workspace access, or how removal works (the schema's 'null' value does that job, not the description).

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 contains no filler, but it is under-specified rather than efficient — the brevity costs information rather than saving it. Structure is fine; content is thin.

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 three-required-parameter permission mutation with no annotations, one sentence is not enough; an agent cannot judge safety, required role, or side effects. An output schema exists, so return values need not be explained, but the behavioral and usage gaps remain.

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% and each of the three parameters is documented in the schema itself, including the notable 'null pour supprimer' on access_level. The description adds no additional meaning, so the baseline 3 applies.

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 gives a specific verb and resource ('Modifie l'accès d'un utilisateur à un espace de travail'), so an agent can tell it grants/changes workspace-level permissions rather than document- or organization-level ones. It stops short of naming the sibling distinction explicitly, but the workspace scope is unambiguous.

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 mention of prerequisites (does the user need an existing account? must the caller be an owner?), and no pointer to the obvious alternatives such as list_workspace_access or modify_document_access. The agent must infer everything from the name.

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