Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Document Access

list_document_access

Lists users with access to a Grist document to audit permissions and identify authorized accounts.

Instructions

Liste les utilisateurs ayant accès à 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>"
    },
    "name": "list_document_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full behavioral burden and says nothing about required permissions, whether inherited workspace or organization access is included in the result, or whether the list is paginated. For an access-inspection tool, whether inherited grants appear is the single most decision-relevant behavior and it is unstated.

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 front-loaded sentence with no padding, but it is thin enough that it reads as under-specified rather than deliberately tight. Nothing is wasted, yet nothing is added either.

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

Completeness3/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, and a one-parameter read tool is low complexity. The remaining gap is the access-scoping semantics (inherited vs. direct grants) that an agent would need before trusting the result.

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 one parameter with 100% schema description coverage, so the schema already explains doc_id. The description contributes no additional meaning about the parameter, which matches the baseline for fully documented schemas.

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?

States a specific verb ("Liste") and resource ("les utilisateurs ayant accès à un document") tied to a doc_id, so the operation is immediately understood. It does not explicitly distinguish itself from the sibling scope variants list_workspace_access and list_organization_access, leaving the reader to infer scope from the word "document".

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 or when-not-to-use guidance and no mention of alternatives such as the workspace or organization access listings or the modify_document_access counterpart. Only the implicit read semantics of "Liste" hint at context.

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