Skip to main content
Glama
Rererr

drivelift

by Rererr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import OAuth client JSON

import_client_secret

Copies a downloaded OAuth client JSON into drivelift's config directory. Pass the file path to import the secret without exposing it in conversation; without a path, lists candidates from Downloads.

Instructions

Copy a downloaded OAuth client JSON (Desktop app type) into drivelift's config directory. Pass the file path; the secret itself never enters the conversation. Without a path, it only lists client_secret*.json candidates in ~/Downloads (newest first) and copies nothing — confirm with the user, then call again with the chosen path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to the downloaded client_secret_*.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description carries the behavioral burden and adds valuable context: it copies rather than moves, never exposes the secret in conversation, and copies nothing when the path is omitted. It does not mention overwrite behavior when the config file already exists, so it stops short of full transparency.

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 sentences, front-loaded with the primary action, then the conditional list mode and confirmation step. Every sentence earns its place with no redundant phrasing.

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?

For a single optional parameter with no output schema, this is nearly complete: it covers both call modes, the list output ordering, and the required user-confirmation step. The only gap is unspecified behavior for invalid paths or existing config-file collisions.

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?

The schema already documents path with 100% coverage, so the baseline is 3. The description reinforces that omitting the path triggers listing, but it adds no new format or value constraints 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 states a specific verb and resource: copy a downloaded OAuth client JSON into drivelift's config directory. It also documents the optional list-only mode, making the tool's dual purpose unmistakable and distinct from siblings like upload or auth_start.

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?

It gives explicit invocation rules: call without a path to list candidates, and call with a path to import, including a confirm-then-call-again protocol. It does not explicitly contrast with sibling tools, but the two modes are so clearly specified that an agent knows exactly when to invoke it.

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