Skip to main content
Glama
Grist MCP Server
by nic01asFr

Modify Document Access

modify_document_access

Change a user's access level to a Grist document by email, setting owners, editors, viewers, or removing access.

Instructions

Modifie l'accès d'un utilisateur à un document.

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": {
      "doc_id": "<doc_id>",
      "user_email": "<user_email>",
      "access_level": "<access_level>"
    },
    "name": "modify_document_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
user_emailYesEmail de l'utilisateur
access_levelYesNiveau d'accès (owners, editors, viewers, 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, ou null pour supprimer)"
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / user_email / description
      Added value: +"Email de l'utilisateur"
  2. First observedv0.1.0

TDQS

C2.6/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 for a mutation. It does not state that this is an upsert-style grant, what happens when the user has no prior access, whether the caller needs owner privileges, or that the change is immediately effective. The fact that passing null revokes access appears only in the schema, 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.

Conciseness4/5

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

A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is also the source of the missing guidance rather than a virtue of careful editing.

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 still an unannotated permission-mutation tool. Nothing covers preconditions, side effects, error conditions, or how it relates to the parallel organization/workspace access tools, leaving meaningful gaps.

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 all three parameters (doc_id, user_email, access_level) are already documented, including the enum-like values and null-for-removal. The description adds no additional semantics, which meets the baseline for high-coverage schemas but no more.

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?

"Modifie l'accès d'un utilisateur à un document" gives a verb (modify) and a resource (document access scoped to one user), but it is nearly a restatement of the tool name and title. It does not distinguish itself from siblings such as modify_organization_access, modify_workspace_access, or list_document_access, so the agent must infer that this is the per-document, per-user variant.

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 and no mention of alternatives, even though the sibling list contains three near-identical access-modification tools. Nothing tells the agent when to pick this over modify_workspace_access or when to use list_document_access first to inspect current permissions.

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