Skip to main content
Glama

Google_drive

by io.github.pipeworx-io

Drive List Files

drive_list_files
Read-onlyIdempotent

List files in your Google Drive. Optionally filter by name, type, owner, or modified date (e.g., 'name contains "report"'). Returns file names, IDs, types, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoDrive search query (e.g., "name contains 'report'" or "mimeType='application/pdf'")
order_byNoSort order (e.g., "modifiedTime desc", "name")
page_sizeNoMaximum number of files to return (default 10, max 100)
page_tokenNoToken for fetching the next page of results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection failed
filesNoList of files matching the query
messageNoError message with instructions
nextPageTokenNoToken for fetching the next page of results

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds detail about return fields but doesn't disclose pagination or rate limits beyond schema.

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?

Two sentences, front-loaded with purpose, no redundancy. Every word earns its place.

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?

Given output schema exists, description adequately covers listing with filters and return fields. Lacks mention of pagination (page_token) but schema handles it.

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?

Schema covers all parameters (100% coverage). Description adds value with a concrete example query ('name contains "report"'), aiding interpretation.

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?

Clearly states 'List files in your Google Drive', a specific verb+resource. Differentiates from siblings like drive_search by mentioning optional filters and returning metadata.

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?

Gives context on optional filters (name, type, owner, modified date) with an example, but does not explicitly contrast with siblings like drive_search or drive_get_file.

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

All Google_drive toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer queries, and the multiple polymarket_* tools scan for edges and arbitrage. The Drive tools are distinct, but the surrounding 31 unrelated tools create significant ambiguity about which tool to call for a given task.

Naming Consistency2/5

Tool names are all snake_case, but the pattern is inconsistent: some start with verbs (drive_create_file, ask_pipeworx, validate_claim), some are noun phrases (entity_profile, recent_changes, polymarket_edges), and some are bare verbs (remember, forget, recall). There is no uniform verb_noun convention, and suffixes like _beta and _grounded add further irregularity.

Tool Count1/5

36 tools is far too many for a server named Google_drive, especially since only 5 tools (drive_create_file, drive_get_content, drive_get_file, drive_list_files, drive_search) actually relate to Drive. The other 31 tools cover unrelated domains like Pipeworx data queries, Polymarket betting, and memory management, making the tool count wildly disproportionate to the server's apparent purpose.

Completeness2/5

For a Google Drive server, the tool set is incomplete: it covers create, get content, get metadata, list, and search, but lacks essential operations like updating, deleting, uploading, moving, copying files, creating folders, or managing permissions/sharing. These gaps would force agents to work around missing core Drive functionality.

Resources