Skip to main content
Glama
Sign In
mcp-gmail

mcp-gmail

by knowledgeislands
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

authenticate

Read-onlyIdempotent

Start the OAuth flow to authorize server access to your Gmail account. Required before using other Gmail tools.

Instructions

Start the OAuth flow to authorize this server against your Gmail account

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce re-authentication even if already authenticated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.1/5.0
Behavior1/5

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

The description claims a write operation ('Start the OAuth flow') while annotations state readOnlyHint=true, creating a contradiction. No details on side effects, user interaction, or token handling are provided.

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?

The description is a single sentence that is front-loaded with the key action. It is concise but could be slightly more informative without adding length.

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 low complexity (one optional param, no output schema), the description still lacks critical behavioral details such as whether it opens a browser or returns a URL, and contradicts annotations, making it incomplete.

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 one parameter 'force' having a clear description. The tool description does not add meaning beyond the schema but is adequate.

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 'Start the OAuth flow' and the resource 'authorize this server against your Gmail account', distinguishing it from siblings like 'about' and 'check-auth-status' which are informational or status-checking tools.

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 use for initiating authentication but lacks explicit guidance on when to use it versus alternatives, when not to use it, or prerequisites like needing a Gmail account.

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