Loading ToolBench
Google Drive file operations via Google Drive API v3. Provide a Bearer token in the Authorization header.
Server has 7 well-named tools with verb-leading names (gdrive_list_files, gdrive_read_file, etc.) and clear descriptions. All tools have input schemas with type definitions and parameter descriptions. However, there are notable gaps: output schemas are not formally documented, error handling lacks recovery guidance, and the tool descriptions, while present, are sometimes generic. The gdrive_write_file tool includes a helpful WARNING about auto-created folders, which is good practice. Parameter descriptions are present but could be more specific about formats and constraints (e.g., what constitutes a valid 'path'). The server implements Bearer token authentication properly and manages per-session state via FastMCP's context system, but there is no explicit tool annotations (readOnlyHint/destructiveHint/idempotentHint) in the registered tools despite the risk metadata being documented in the evaluation summary.
Create a folder in Google Drive (including intermediate folders).
Delete a file from Google Drive.
Get file or folder metadata without downloading content.
List files and folders in a Google Drive directory.
Move or rename a file in Google Drive.
Read a file's content and metadata from Google Drive.
Output schemas not formally documented in tool definitions. LLMs cannot predict what fields to expect from tool responses, forcing them to discover response structure by trial and error.
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are not declared in tool definitions. Risk metadata exists in evaluation summary but is not exposed to MCP clients, preventing LLMs from understanding which operations are safe to retry or have side effects.
Error messages are generic (via DriveAPIError.to_dict()). No explicit recovery guidance when a tool call fails, LLMs receive an error but don't know what to do next (retry, try a different tool, ask user).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | A | 81 | <=2025-11-25 | v2 |
| 2026-03-09 | D | 51 | - | v1 |
Create or update a file in Google Drive. WARNING: If the parent folder does not exist, it will be auto-created. Google Drive allows duplicate folder names, so writing to a path when resolution fails may silently create a duplicate folder. To avoid this, verify paths with gdrive_read_file or gdrive_list_files before writing to paths that should already exist.
Parameter 'path' is under-specified. No documentation of expected format (absolute? relative? with or without leading slash?), character restrictions, maximum length, or behavior on special characters. gdrive_write_file's description warns about path resolution but doesn't formalize the constraint.
No pagination support for gdrive_list_files. If a folder contains hundreds of items, the response could exhaust the context window. No limit, offset, or cursor parameters documented.
gdrive_write_file accepts 'etag' parameter for optimistic concurrency but provides no guidance on when to use it or how to handle conflict responses. Error case when etag doesn't match is not documented.