Skip to main content
Glama
ktibbs9417

GAM MCP Server

by ktibbs9417
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_shared_drive_members

Audit members of a Google Shared Drive, listing their roles and access levels, and output results to a Google Sheet for review.

Instructions

    Step 10 — List existing Shared Drives and their members.

    Confirms the destination Shared Drive exists and who has what level
    of access.  The migrating user must be a Manager on the Shared
    Drive to move files into it.

    Args:
        user_email: The email of the admin user running the query.
        sheet_id: The ID of the Google Sheet for output.
        sheet_name: The tab name (default: "shared_drive_members").

    GAM command:
        gam user <user_email> print teamdriveacls
            fields "id,name,role,type,emailAddress"
            todrive tdfileid <sheet_id> tdsheet "<sheet_name>"
            tdupdatesheet tdretaintitle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
sheet_nameNoshared_drive_members
user_emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.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 bears full responsibility. It implies a read operation ('List', 'Confirms') but does not explicitly state it is non-destructive or mention side effects like overwriting sheet data. The write to Google Sheets is a behavioral trait that should be disclosed.

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?

The description is clear but includes a verbose GAM command block that is not essential for an AI agent's understanding of the tool's purpose or invocation. It could be more concise by omitting the implementation detail.

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?

Covers tool purpose, parameters, and usage context (migration step). With an output schema present, return values need not be explained. Lacks details on error conditions or what happens if the user is not a Manager, but overall sufficient for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description explains all three parameters clearly: user_email ('admin user running the query'), sheet_id ('Google Sheet for output'), and sheet_name (with default). This adds essential meaning beyond the schema's bare titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists existing Shared Drives and their members, which distinguishes it from sibling audit tools focused on permissions, files, or other entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context: it's step 10 in a migration process, confirms destination drive existence and access levels, and states the prerequisite that the migrating user must be a Manager on the drive. No explicit alternatives or when-not-to-use, but clear usage scenario.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ktibbs9417/gamcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server