Skip to main content
Glama

drive_search

Read-onlyIdempotent

Search the workspace's registered Google Drive folders by words in the name or the text. Only files inside a registered folder are returned. folder narrows the search to ONE registered root (pass the root's id or link); to look inside a sub-folder use drive.list on it. truncated: true means the search stopped before Google ran out of results: narrow the query. Search by text may not see changes made in the last few minutes (names are found at once); drive.read always reads the current text.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return (1-100).
queryYesWords to look for in file names and text.
folderNoA registered root (id or link) to search in. Not a sub-folder.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations (which already declare read-only, idempotent, closed-world). The description discloses that results are limited to registered folders, that `truncated: true` means the result set was cut short by the tool rather than by Google, and that text search can lag behind very recent edits while name matching is immediate.

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?

Scope and the registered-folder restriction are front-loaded, then each subsequent sentence adds a distinct actionable fact (folder narrowing, truncation meaning, staleness vs drive.read). No filler and no repetition of the schema.

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?

For a four-parameter search tool with no output schema, the description still explains the one meaningful return signal (`truncated`), the index lag caveat, and how to escalate to drive.read for fresh content. An agent has everything needed to call it correctly and interpret the response.

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%, so the baseline is 3, but the description adds real meaning for `folder`: it must be ONE registered root, accepts an id or a link, and must not be a sub-folder. `limit` and `in_workspace` are left entirely to the schema, so it stops short of a 5.

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?

States a specific verb and resource ('Search the workspace's registered Google Drive folders by words in the name or the text') and immediately scopes it ('Only files inside a registered folder are returned'). It also distinguishes itself from drive.list (sub-folders) and drive.read (current text), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use `folder` to restrict to one registered root, use drive.list to descend into a sub-folder, and use drive.read when current text is required rather than indexed text. Exclusions (sub-folders not searched) are stated, not implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.