Skip to main content
Glama

drive get file

drive_get_file
Read-onlyIdempotent

Retrieve metadata for one Google Drive file, including owners, size, and web link, to inspect details before sharing or auditing access.

Instructions

Fetch metadata for a single Drive file, including owners, size and web link.

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

Input Schema

NameRequiredDescriptionDefault
file_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so safety is fully covered. The description adds only the field inventory, which the existing output schema already documents, and says nothing about what happens when the file is missing, inaccessible, or trashed, nor about the openWorld/shared-drive implications.

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 short sentence, front-loaded with the verb and resource, with zero filler. Nothing in it is redundant with siblings or restates the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The return values are covered by an existing output schema, so the description need not restate them. However, the undefined file_id semantics and the absence of any routing among the many drive_* metadata/list/read siblings leave real gaps for a read tool in a dense toolset.

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 coverage is 0% for the single required parameter file_id, so the description carries the full burden and does not meet it. It never explains whether file_id is a Drive ID, a path, or a name, nor what input shape will succeed, leaving the only parameter ambiguous.

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?

States a specific verb and resource ('Fetch metadata for a single Drive file') and names the returned fields (owners, size, web link), so the agent knows exactly what it gets. It does not distinguish itself from drive_list_files, drive_search_files, or drive_read_file, which is the main clarity gap in a crowded sibling set.

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 when-to-use guidance and no mention of alternatives. An agent must infer that this is the single-file, metadata-only path versus drive_list_files/search for discovery and drive_read_file for content; nothing in the description confirms or excludes those cases.

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