Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Organization Access

modify_organization_access

Update a user's access level to a Grist organization, or remove their access by setting the level to null.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
org_idYesL'ID de l'organisation
user_emailYesEmail de l'utilisateur
access_levelYesNiveau d'accès (owners, editors, viewers, members, ou null pour supprimer)

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, members, ou null pour supprimer)"
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation"
    • addedInput schema / properties / user_email / description
      Added value: +"Email de l'utilisateur"
  2. First observedv0.1.0

TDQS

C2.7/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, yet it says nothing about required permissions, whether changing access is reversible, or what happens to the user when access is removed (the null-removal behavior lives only in the schema). It correctly implies a mutation but discloses nothing beyond that.

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?

A single efficient sentence with no padding, but it is under-specified rather than concise, and it is written in French while the tool names and sibling catalog are in English, creating a needless language mismatch for the calling agent.

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

Completeness4/5

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

3 required params, 3 named in schema, output schema exists

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 org_id, user_email, and access_level (including 'null pour supprimer') are already documented in the schema. The description adds no parameter meaning on top of that, so the baseline 3 applies.

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 description names a verb and resource ('Modifie l'accès ... à une organisation') but is essentially a French restatement of the title 'Modify Organization Access'. It adds only 'd'un utilisateur', and gives no basis for distinguishing it from siblings like modify_workspace_access or modify_document_access.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance is present. An agent must infer from the tool name alone that this is the org-scoped counterpart to the workspace/document access modifiers.

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