Skip to main content
Glama

drive share file

drive_share_file

Grant a user or domain access to a Drive file by assigning a role; optionally notify them, with the access change audited.

Instructions

Grant a user or domain access to a Drive file. Access-control change; audited.

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_share_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoreader
emailNo
domainNo
file_idYes
send_notificationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds genuinely new context with "Access-control change; audited", but says nothing about required permission level to share, whether re-granting a role is additive, or what happens when neither grantee field is supplied. Adds some value but not rich behavioral context.

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 short sentences, front-loaded with the action and resource, with the behavioral tag appended. No filler or repetition of the title.

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?

This is a five-parameter mutation tool with zero schema description coverage and no enum documentation; the presence of an output schema removes the need to describe returns, but the input side is badly under-specified for a permissions-changing operation. Missing role options, grantee precedence, and notification behavior make the definition insufficient to call confidently.

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 description coverage is 0% across five parameters, so the description must carry the burden and largely fails: it hints at role and grantee types but never enumerates valid role values (reader/writer/owner), never explains mutual exclusivity of email vs domain, and never mentions send_notification or the file_id requirement. The agent must open the schema and guess at semantics.

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?

The description gives a specific verb and resource ("Grant ... access to a Drive file") and even specifies the two grantee types (user or domain), so an agent knows this is an access-granting mutation. It does not explicitly contrast itself with the closest sibling, drive_list_permissions, so it falls short of a 5.

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 only implied: the agent can infer this is the tool for adding a share, but there is no explicit "use this when X, use Y instead" routing, no note about checking existing permissions first, and no exclusions. Adequate but leaves the agent to reason about alternatives.

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