Skip to main content
Glama
dipseth

google-workspace-unlimited

Google Drive Auth Status Check

check_drive_auth
Read-onlyIdempotent

Verify Google Drive authentication status for a user account, with optional cross-OAuth access using a passphrase.

Instructions

Verify Google Drive authentication status for a specific user account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailNoThe user's Google email address for Drive access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).
cross_oauth_passwordNoPassphrase for cross-OAuth account access. Required when the linked account owner set a passphrase during their start_google_auth setup. Only alphanumeric, underscore, and hyphen allowed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if authentication check failed
scopesNoOAuth scopes granted for the checked account's credentials
messageYesHuman-readable message describing the authentication status
sessionIdNoSession UUID for this connection. Save this to reconnect with same tool state using ?uuid= parameter
userEmailYesGoogle email address that was checked for authentication
authMethodNoHow this session authenticated: 'oauth' (browser flow), 'api_key' (shared MCP_API_KEY), or 'user_api_key' (per-user key)
authenticatedYesWhether the user is currently authenticated with valid credentials
keyBoundEmailNoFor per-user API key sessions, the email the key is bound to
linkedAccountsNoOther email accounts accessible via account linking (per-user key sessions)
crossOAuthLinkageNoCross-OAuth linkage configuration for this account
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true, and destructiveHint as false. The description's 'Verify' aligns with these, but adds no new behavioral information beyond what annotations provide.

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?

The description is a single sentence without any extraneous information. Every word is necessary and front-loaded.

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

Completeness4/5

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

Given the tool's low complexity and existence of an output schema, the description covers the core purpose adequately. However, it does not mention the returned status values or any prerequisites, leaving a slight gap.

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 detailed descriptions for both parameters (user_google_email and cross_oauth_password). The description does not add additional meaning beyond the schema.

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 'Verify' and the resource 'Google Drive authentication status', and specifies the scope 'for a specific user account'. It distinguishes this tool from sibling tools that perform other drive operations like listing or creating files.

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?

The description implies usage for checking auth status before other drive operations but does not explicitly state when to use or not use this tool, nor does it mention alternatives. The guidance is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipseth/google_workspace_fastmcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server