Skip to main content
Glama

google_disconnect_account

Disconnects a Google account from Local MCP by removing its Keychain sign-in and revoking access at Google.

Instructions

(Beta) Disconnect a Google account from LMCP: its sign-in is removed from the Keychain and revoked at Googl...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does contribute real behavioral context: the sign-in is removed from the Keychain and revoked at Google, which tells the agent this has external, credential-level consequences. However, it does not state irreversibility, whether dependent services (Gmail, Drive, Calendar) lose access, or what the response looks like — and the truncation cuts off exactly where further consequences would likely be disclosed.

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?

One front-loaded sentence that leads with the beta marker, the verb, and the resource, then appends the effect. There is no filler, though the text is truncated, which is a defect in delivery rather than verbosity.

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?

This is a destructive, credential-revoking operation with no annotations and no output schema, so the description is the only place an agent can learn about consequences. It gives the key ones (Keychain removal, Google-side revocation) but leaves irreversibility, affected downstream services, and the target-account question unresolved, and the trailing truncation means the definition is literally incomplete.

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 schema has zero parameters at 100% coverage, so there is nothing for the description to document and the baseline of 4 applies. A residual ambiguity is that 'a Google account' is undefined when multiple accounts exist and no parameter selects one, but zero-param tools are typically default-scoped.

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 names a specific verb and resource ('Disconnect a Google account from LMCP') and distinguishes it implicitly from google_connect_account and from the many other service-specific disconnect_* siblings. The added detail about sign-in removal and revocation sharpens the scope, though the text is visibly truncated mid-sentence ('revoked at Googl...'), so the full purpose statement is not available.

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 by the name and first clause — an agent can infer this is the teardown counterpart to google_connect_account. There is no explicit when-to-use, no when-not-to-use, no mention of preconditions (e.g. what happens if no Google account is connected), and no named alternative such as gdrive_disconnect for narrower integrations.

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