Skip to main content
Glama
Grist MCP Server
by nic01asFr

List Organization Access

list_organization_access

Lists users who have access to a Grist organization using its org ID, so you can audit membership and permissions.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
org_idYesL'ID de l'organisation

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / org_id / description
      Added value: +"L'ID de l'organisation"
  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?

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about required permissions, whether inherited access (via workspaces or documents) is included, or whether results are paginated. Only the basic read-only nature is implied by 'Liste'. An output schema exists, so return shape need not be described, but the access-scope semantics remain unaddressed.

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 zero filler. It is efficient, though its brevity borders on under-specification rather than tightness, which is penalized elsewhere rather than here.

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?

A one-parameter read tool with an output schema and full schema coverage is a low-complexity case, so the description is close to sufficient. However, it leaves open whether the listing covers direct or inherited organization access, which is the key ambiguity for an access-listing tool and is not resolved by the schema.

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 coverage is 100% with a single documented org_id parameter (accepting integer or string), so the schema already does the explanatory work. The description adds no format, ID-source, or lookup guidance beyond what the schema states. 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?

States a specific verb and resource: listing users who have access to an organization. An agent can distinguish it from the modify_organization_access sibling by the verb alone. It does not explicitly contrast with the analogous list_document_access / list_workspace_access variants, but the resource 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 prerequisite mention, and no reference to alternatives such as modify_organization_access or the document/workspace equivalents. The intended usage is only inferable from the verb 'Liste' and the resource name.

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