Skip to main content
Glama
Sign In
fastmcp-gsuite

fastmcp-gsuite

by tumf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_drive_file

Retrieve metadata for a Google Drive file by its ID and user email. Returns file name, type, size, and modification times.

Instructions

Get metadata for a specific Google Drive file by its ID.

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

Input Schema

NameRequiredDescriptionDefault
user_idYesThe EMAIL of the Google account. Choose from:
file_idYesThe unique ID of the Google Drive file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It states 'Get metadata' but does not explicitly confirm it is read-only, nor does it disclose any behavioral traits like permissions required, error cases, or side effects. Minimal disclosure beyond the obvious action.

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?

One sentence, no waste. Clearly front-loaded with the action and resource. Every word earns its place.

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?

No output schema, so description should explain what metadata is returned (e.g., name, type, size). It does not. Also lacks prerequisites like file existence or access rights. Incomplete for a get operation.

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%, so baseline is 3. The description adds no extra meaning beyond the schema: 'by its ID' mirrors the file_id parameter, and user_id is described as email in both. No added value beyond what the schema already provides.

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?

The description clearly states the verb 'Get', resource 'metadata for a specific Google Drive file', and method 'by its ID'. It distinguishes from siblings like 'list_drive_files' (list) and 'download_drive_file' (download).

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?

No explicit guidance on when to use this tool versus alternatives. For example, it does not mention that 'download_drive_file' should be used for content retrieval. The description implies usage for metadata retrieval but provides no exclusions or context.

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

Deploy Server

Other Tools