Skip to main content
Glama

google_connect_account

Connects a Google account (Gmail or Google Workspace) to Local MCP so the Google Calendar tools can access your calendars.

Instructions

(Beta) Connect a Google account (Gmail address or Google Workspace) to LMCP for the Google Calendar tools (...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses only '(Beta)' and the general act of connecting — nothing about the OAuth/consent flow, whether credentials are stored, whether it overwrites an existing Google account, or what the caller gets back.

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

Conciseness3/5

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

The opening is front-loaded and efficient, but the text terminates mid-clause with an unbalanced parenthesis ('...the Google Calendar tools (...'), so the one sentence does not actually resolve. Brevity here reads as truncation rather than tight writing.

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?

For a zero-parameter connect tool with no annotations and no output schema, the definition should explain the account-connection flow and any prerequisites. Instead it stops mid-sentence and omits everything an agent would need to invoke it confidently, such as authentication requirements or account-state effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description's mention of 'Gmail address or Google Workspace' hints at the account type involved, but with no input schema properties there is nothing more that needs documenting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Connect a Google account (Gmail address or Google Workspace) to LMCP,' and scopes the purpose to 'the Google Calendar tools,' which distinguishes it from disconnect/connect-M365 siblings. It does not explicitly name the sibling it complements, and the trailing parenthesis leaves the statement unfinished.

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?

Usage is only implied through 'for the Google Calendar tools,' which suggests connecting when Calendar access is needed. It never states prerequisites, when not to use it, or how it relates to google_disconnect_account or the other connect_* tools, and the cut-off sentence likely removed further guidance.

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