Skip to main content
Glama

drive search files

drive_search_files
Read-onlyIdempotent

Searches Google Drive by file name or full text and returns read-only metadata, helping you locate files without modifying content.

Instructions

Search Drive by file name or full text. Read-only; returns metadata only.

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": {
      "query": "<query>"
    },
    "name": "drive_search_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so "Read-only" restates structured data rather than adding to it. "Returns metadata only" does add real value by telling the agent it must switch to drive_read_file for content, but nothing is said about result caps, latency, or pagination behavior.

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?

Two short sentences with the behavioral caveat front-loaded and zero filler. It is efficient, though the terseness is part of why the query semantics are left ambiguous.

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?

An output schema exists, so return values need not be described, and the metadata-only note covers the key expectation. However, with 0% parameter coverage, the definition should clarify query syntax and page_size behavior to be fully actionable.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters. The description hints that query matches file names or full text, which is genuinely useful, but it never states whether query is plain text or Drive query syntax, and page_size goes entirely unexplained in both schema and description.

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?

Names a specific verb and resource ("Search Drive") and narrows the match surface to file name or full text, which is enough to separate it from list-style siblings like drive_list_files. It falls short of explicit sibling differentiation, since no alternative tool is named.

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 phrase "by file name or full text" implies when this tool applies (locating files by name or content), but there is no explicit when-to-use/when-not guidance and no pointer to drive_list_files, drive_get_file, or drive_read_file for the adjacent jobs.

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