Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Workspace Access

list_workspace_access

Lists all users who have access to a specified Grist workspace, helping you audit permissions and identify workspace collaborators.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
workspace_idYesL'ID de l'espace de travail

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / workspace_id / description
      Added value: +"L'ID de l'espace de travail"
  2. First observedv0.1.0

TDQS

C2.5/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 burden, yet it says nothing about whether access listings require elevated permissions, whether results are paginated, or how large access lists behave. It confirms only that this is a read of users, which is the bare minimum beyond the name.

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 short sentence with no filler, so nothing is wasted, but the brevity comes at the cost of under-specification rather than efficient information density.

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?

The tool is simple (one required ID, output schema present), so the bar is low, but with zero annotations and no usage or permission context the definition still leaves an agent without enough to decide when this tool, rather than modify_workspace_access or a sibling list tool, is the right call.

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?

Only one parameter exists and the schema already documents it at 100% coverage ('L'ID de l'espace de travail'), so the description cannot add meaning there. It also does not clarify whether workspace_id accepts a numeric ID only or a name/alias.

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 sentence names a specific verb+resource ('Liste les utilisateurs ayant accès à un espace de travail'), so the operation is understandable. But it is essentially a French restatement of the title with no differentiation from close siblings like list_document_access or list_organization_access, leaving the agent to infer scope from names alone.

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 (e.g. admin rights needed to see access lists), and no pointer to the modify_workspace_access counterpart. The agent must guess the context entirely.

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