Skip to main content
Glama

search_drive_rag

Read-onlyIdempotent

Search workspace documents, Docs, Sheets, and Slides by query to retrieve relevant content for AI agent grounding and workspace retrieval.

Instructions

Search workspace documents, Docs, Sheets, and Slides.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already communicate read-only, idempotent, non-destructive, closed-world behavior, and the description consistently adds the document corpus and supported content types. It does not explain retrieval behavior, ranking, indexing freshness, permissions, or whether results contain files, excerpts, or generated answers.

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?

The single sentence is direct, readable, and free of redundant wording. Its brevity is efficient, though it leaves out operationally important details rather than achieving the completeness expected of a top score.

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?

An agent can infer that a required query and optional limit are needed, but the definition does not adequately explain the RAG search behavior, result contents, query expectations, or limits on result count. These gaps matter because neither parameter descriptions nor an output schema supplies the missing information.

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?

With 0% schema description coverage, the description needed to compensate but never mentions either query or limit. The corpus description gives some implicit meaning to query, yet there is no guidance on query wording or search syntax, and limit has no documented semantics beyond its numeric type and default in the schema.

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 gives a clear verb and resource: searching workspace documents, Docs, Sheets, and Slides. It does not distinguish this tool from siblings such as list_drive_workspace, read_drive_file, or the other search tools, nor clarify what the RAG variant retrieves.

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?

There is no explicit guidance about when to choose this tool, what kinds of queries it handles best, or when listing or reading files would be more appropriate. The searchable content types imply a general use case, but provide no meaningful selection guidance among alternatives.

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