gg-mcp

by tannht

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

search_documents

Search Google Docs in Drive by query, or leave query empty to list recently accessed documents.

Instructions

Search for Google Docs documents in Drive. Empty query lists recent docs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_documents"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`max_results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, description carries full burden. It discloses empty query lists recent docs, but no details on auth, rate limits, or safety. Lacks behavioral depth.

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, no fluff. Efficiently conveys core purpose and a key behavioral detail.

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?

Low schema coverage, no annotations, no output schema. Description fails to explain return format or additional context needed for full understanding.

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 has 0% description coverage for parameters. Description adds no meaning to 'query' or 'max_results' beyond their names and defaults, leaving agents uninformed.

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?

Description clearly states verb 'Search' and resource 'Google Docs documents in Drive', distinguishing from siblings like search_drive, search_presentations, search_spreadsheets. It also adds behavior for empty query.

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?

Implies usage for searching Google Docs and notes empty query behavior, but no explicit guidance on when not to use or alternatives like search_drive for other file types.

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