Skip to main content
Glama
andresfrei

Google Drive MCP Server

by andresfrei

list_drives

Display all configured Google Drive accounts available for access through the MCP server. Use this tool to view which connected drives you can interact with for file operations.

Instructions

List all configured Google Drive accounts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the list_drives tool. It retrieves the list of configured Google Drive accounts using drivesConfigLoader.listDrives(), formats the output as structured content, and provides a text response indicating if no drives are configured.
    handler: async () => {
      const drives = drivesConfigLoader.listDrives();
      const output = { drives };
    
      return {
        content: [
          {
            type: "text" as const,
            text:
              drives.length === 0
                ? "No drives configured yet. Use add_drive to add a Google Drive account."
                : JSON.stringify(output, null, 2),
          },
        ],
        structuredContent: output,
      };
    },
  • The tool configuration including inputSchema (empty) and outputSchema defining an optional array of drive objects with id, name, and optional description.
    config: {
      title: "List Google Drive Accounts",
      description: "List all configured Google Drive accounts",
      inputSchema: {},
      outputSchema: {
        drives: z
          .array(
            z.object({
              id: z.string(),
              name: z.string(),
              description: z.string().optional(),
            })
          )
          .optional(),
      },
  • Dynamic registration of all MCP tools (including list_drives) imported from tools/index.ts. Loops through all exported tools and calls server.registerTool for each.
    const toolList = Object.values(tools);
    toolList.forEach((tool) => {
      server.registerTool(tool.name, tool.config as any, tool.handler as any);
    });
  • Central tools index exports listDrivesTool, making it available for bulk import and registration in the MCP server.
    export { listDrivesTool } from "@/mcp/tools/list-drives.js";
  • Helper method in DrivesConfigLoader that lists all configured drives, mapping config entries to simplified {id, name, description} objects.
    listDrives() {
      const config = this.getConfig();
      return Object.entries(config.drives).map(([id, cfg]) => ({
        id,
        name: cfg.name,
        description: cfg.description,
      }));
    }
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 burden of behavioral disclosure. It states it lists drives but doesn't cover aspects like authentication requirements, rate limits, pagination, or what 'configured' entails. This leaves significant gaps for a tool that likely interacts with external services.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the tool has 0 parameters and no output schema, the description is minimally adequate but incomplete. It lacks details on behavioral aspects like authentication or return format, which are important for a tool listing external resources. The absence of annotations increases the need for more context.

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

Parameters4/5

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

The tool has 0 parameters, and the schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it could slightly clarify the scope of 'configured' (e.g., user-specific vs. system-wide).

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 clearly states the verb ('List') and resource ('Google Drive accounts') with the scope modifier 'all configured', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_files' or 'search_files', which might also involve listing operations.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_files' or 'search_files', nor does it mention prerequisites such as needing configured drives first. It lacks explicit context or exclusions, leaving usage ambiguous.

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/andresfrei/mcp-google-drive-server'

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