Skip to main content
Glama
Sign In
gg-mcp

gg-mcp

by tannht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_drive_folders

List all folders in a Google Drive account, starting from a parent folder or the root.

Instructions

List all folders in Google Drive. parent_id: 'root' for main folder.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_drive_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
parent_idNoroot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.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 present, so the description must fully disclose behavior. It only states that it lists folders, but does not mention whether the listing is recursive, if trashed items are included, required permissions, or any side effects. This is insufficient for a mutation-free list operation with no annotations.

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 extremely concise with two sentences, no wasted words, and the core action is front-loaded. It earns its space.

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?

For a list tool with one parameter and no output schema, the description is incomplete. It does not explain the output format, pagination, recursion, or filtering. Given the many sibling tools, more context on when this tool is appropriate (e.g., flat vs recursive) would improve completeness.

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?

The schema has one parameter parent_id with default 'root' and no description. The description adds context by noting that 'root' is for the main folder, but does not explain other possible values or the effect of the parameter. Schema description coverage is 0%, so the description adds some value but is minimal.

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 it lists all folders in Google Drive, which is a specific verb+resource. It mentions parent_id with 'root' for main folder, providing context. However, it does not explicitly differentiate from sibling tools like search_drive or get_document, but the action is distinct enough.

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 gives a hint about parent_id default but does not specify when to use this tool versus alternatives like search_drive. No when-not or explicit guidance for usage scenarios is provided.

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