Skip to main content
Glama
Sign In
drive-mcp

drive-mcp

by reisbel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_file_permissions

Retrieve file permissions for a specific Google Drive file to identify who can access it and their assigned role.

Instructions

Who can access a file and with what role.

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": {
      "fileId": "<fileId>"
    },
    "name": "get_file_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a read-only operation but doesn't state whether it requires specific permissions, what the return format is, or any behavioral traits. Minimal disclosure beyond the basic purpose.

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?

The description is a single, efficient sentence that is front-loaded and contains no waste. It's appropriately sized for a simple tool.

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?

Given no annotations, no output schema, and 0% schema coverage, the description is incomplete. It should describe the return structure (e.g., list of users and roles) and any prerequisites. As is, an agent lacks necessary context to invoke confidently.

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 0%, and the description doesn't explain the 'fileId' parameter. However, the parameter name is self-explanatory, and baseline for 1 parameter is typically low. The description adds no meaning beyond the schema.

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?

The description 'Who can access a file and with what role' clearly states the tool retrieves file permissions, a specific resource distinct from siblings like get_file_metadata or share_file. It implies a read operation but doesn't explicitly name the verb 'get' as the name does, slightly reducing clarity.

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?

No guidance on when to use this tool versus alternatives like get_file_metadata or share_file. The description doesn't specify prerequisites such as authentication or ownership.

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

Deploy Server

Other Tools