Google Sheets and Drive MCP

Overview Schema Source Related Servers Discussions Admin

grant_read_access

Grant a specific user read-only access to a Google Sheets spreadsheet via Google Drive. Provide the spreadsheet ID and user email to share without editing permissions.

Instructions

Grant a user reader access to the entire spreadsheet through Google Drive.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "email": "<email>"
    },
    "name": "grant_read_access"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes
`spreadsheet_id`	Yes
`send_notification_email`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden but only states the high-level effect. It omits important behaviors such as whether the user is added as a collaborator, whether a notification email is sent (though hinted by the schema parameter), and what happens if access already exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it is too brief to be informative. It would benefit from additional detail without losing conciseness.

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?

Given the tool's purpose (sharing) and the presence of an output schema, the description lacks crucial context such as required permissions, side effects on existing permissions, and behavior for invalid inputs. It is insufficient for a complete understanding.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description adds no information about the parameters. Parameter names are self-explanatory, but the description fails to clarify format, constraints, or usage beyond the schema titles.

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 and specifically states the action (grant), resource (reader access to the entire spreadsheet), and method (through Google Drive). It effectively distinguishes the tool from siblings, which focus on data manipulation rather than sharing.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., required permissions), and no exclusions. The agent is left without context for decision-making.

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