Skip to main content
Glama

authenticate_google

Idempotent

Checks Google Contacts login status or launches a local browser sign-in using OAuth2 PKCE, saving tokens locally for authenticated requests.

Instructions

Check Google Contacts login status or launch a local browser window on the machine to sign in to Google Contacts (OAuth2 + PKCE) and save tokens locally to ~/.config/google-contacts-mcp/.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "authenticate_google"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceReauthNoIf true, launches the browser login flow even if already authenticated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Beyond annotations, it discloses that a real browser window opens on the local machine, that the flow is OAuth2 with PKCE, and that tokens persist at ~/.config/google-contacts-mcp/ – important side-effect and storage details the annotations do not convey. It is consistent with readOnlyHint=false, since the tool writes token files.

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?

A single front-loaded sentence covering both modes with no filler. It is somewhat run-on with the parenthetical and path, but every clause carries information.

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

Completeness3/5

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

There is no output schema, and the description never says what a status check returns (boolean, account email, error shape) or what a failed browser flow looks like. Given no annotations explain return values, that omission leaves a real gap for an agent deciding next steps.

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% and forceReauth is fully documented in the schema, including the 'even if already authenticated' behavior. The description implies the two modes but adds no syntax or default detail beyond what the schema already provides, so baseline 3 applies.

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?

States specific verbs and resources: checks Google Contacts login status or launches a local browser OAuth2+PKCE sign-in and writes tokens to a stated path. This is unmistakably different from all siblings, which are contact CRUD/search tools.

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?

Makes clear the two conditions under which it is used: verifying whether the user is signed in, or initiating sign-in when they are not. It stops short of explicitly telling the agent to call it before CRUD tools or what to do on failure, but the context is unambiguous.

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