Skip to main content
Glama
Rererr

drivelift

by Rererr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start Google sign-in

auth_start

Begin Google OAuth sign-in to connect your Drive. Opens consent page in browser, waits for approval, then returns completed or pending status for further waiting.

Instructions

Begin the OAuth sign-in. Opens the Google consent page in the user's browser (loopback redirect on 127.0.0.1) and waits up to wait_seconds (default 90) for the user to finish; if they do, the result is state: completed and no further call is needed. Otherwise state: pending — call auth_status (with wait_seconds) to keep waiting. Requires an OAuth client (see status).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
open_browserNoDefault true. Set false to only return the URL.
wait_secondsNoSeconds to wait for the sign-in to finish before returning (default 90, 0 = return immediately).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint:false, openWorldHint:true), the description discloses the browser opening, loopback redirect, waiting behavior, and state outcomes (completed/pending). It also mentions the need for an OAuth client, adding valuable context beyond the structured fields.

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

Conciseness4/5

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

Three sentences, no waste, and the core purpose is front-loaded. It includes necessary details (loopback, wait, states) without fluff, striking a good balance between completeness and brevity.

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?

With no output schema, the description explains the state machine (completed/pending) and the waiting behavior. It covers the prerequisite and points to status and auth_status. It does not mention error conditions explicitly, but the overall flow is sufficiently clear for an agent to call the tool correctly.

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 both parameters fully documented. The description adds no new parameter-level meaning; it merely reinforces the behavior of wait_seconds. Baseline 3 is appropriate since the schema already carries the semantics.

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 'Begin the OAuth sign-in' with a specific verb and resource, and distinguishes itself from siblings by referencing auth_status for the pending state and status for the client prerequisite. It leaves no ambiguity about the tool's role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to call auth_status (when state is pending) and notes the prerequisite of an OAuth client (see status). It does not contrast with all siblings, but the flow is clear and actionable.

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