fastmcp-gsuite

by tumf

Overview Schema Source Related Servers Discussions Admin

Python

Remote

trash_drive_file

Move a file to Google Drive trash. Provide the file ID and user email to soft delete the file.

Instructions

Move a file to Google Drive trash (soft delete).

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": {
      "user_id": "<user_id>",
      "file_id": "<file_id>"
    },
    "name": "trash_drive_file"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	The EMAIL of the Google account. Choose from:
`file_id`	Yes	ID of the file to move to trash.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations present, so description carries full burden. It discloses the key behavioral trait (soft delete), implying reversibility, but does not mention authorization, rate limits, or side effects.

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?

Single sentence of 11 words, no fluff, perfectly concise and front-loaded.

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 simple tool with two string parameters and no output schema, the description covers all needed context: what it does, that it's a soft delete, and implicitly the parameters are clear from schema.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds no further meaning beyond the schema, so baseline 3 applies.

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 the action (move to trash) and resource (file), with explicit mention of 'soft delete' which distinguishes it from permanent deletion siblings like delete_drive_file.

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?

Usage is implied by describing the operation as soft delete, but no explicit guidance on when to use this vs alternatives (e.g., delete_drive_file, untrash_drive_file) is provided.

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