Skip to main content
Glama

Google_drive

by io.github.pipeworx-io

Drive Search

drive_search
Read-onlyIdempotent

Search Drive files by name, type, owner, modified date, or full text using query operators (e.g., 'name contains "report"', 'mimeType = application/pdf'). Returns matching files and IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesDrive search query (e.g., "fullText contains 'quarterly report'" or "modifiedTime > '2024-01-01'")
page_sizeNoMaximum number of results (default 10, max 100)

Output Schema

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

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and behavior. The description adds that it returns matching files and IDs but does not elaborate on pagination, result size limits (only mentioned in page_size), or response format beyond IDs. With rich annotations, the description adds modest value.

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, every word earns its place. The tool's purpose and return value are front-loaded, making it easy for an agent to parse quickly. No unnecessary text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (search with query operators), the description, schema, and annotations together provide comprehensive guidance. The output format (matching files and IDs) is mentioned. The agent has enough information to use the tool correctly.

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 coverage is 100% with descriptions for both parameters. The description goes beyond the schema by providing concrete query operator examples (e.g., 'name contains', 'mimeType =') and mentioning full text search, which adds meaning for the agent. Examples in the schema also help.

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 the verb 'Search' and the resource 'Drive files', listing specific search criteria (name, type, owner, modified date, full text) and mentioning query operators. This distinguishes it from siblings like drive_list_files (which likely lists all files without query operators) and drive_get_file (single file).

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

Usage Guidelines3/5

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

The description implies usage for query-based searching but does not explicitly state when to use this tool versus alternatives like deep_research or search_within. No exclusions or comparisons are provided, leaving the agent to infer context.

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