Skip to main content
Glama
Sign In

Higgs Hub

by pro.higgshub
OverviewDiscussionsAdmin

Disconnect mailbox

disconnect_mailbox
Destructive

Disconnect a mailbox from a workspace you own: once approved, this revokes the stored grant at the provider (Google) and deletes the stored tokens. The mailbox can be reconnected later from the dashboard. Owners only, signed in over OAuth — API keys can't do this. This only stages a request: the owner opens the link in their browser, reviews it, and approves it there with their agent PIN. Never ask for or accept the PIN in chat.

Input Schema

NameRequiredDescriptionDefault
mailboxYesEmail address of the connected mailbox to disconnect.
providerNoOnly needed when the same address is connected under more than one provider.
workspaceNoWhich workspace, by name or id. Only needed when you own more than one — list_workspaces shows them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"Only needed when the same address is connected under both providers."New value: +"Only needed when the same address is connected under more than one provider."
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "google",
-  "microsoft"
-]New value: +[
+  "google",
+  "microsoft",
+  "agentmail"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by disclosing exactly what is destroyed (grant revoked at the provider, stored tokens deleted), that the action is reversible via dashboard reconnection, the owner/OAuth requirement, and the two-phase approval flow (stages a request, owner approves in-browser with an agent PIN, never collect the PIN in chat). This is unusually rich behavioral disclosure for a mutation tool.

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?

Four sentences, each carrying distinct information: the action and its effect, reversibility, auth constraint, and the approval-flow safety rule. The critical effect and constraint are front-loaded with no filler.

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

Completeness5/5

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

For a destructive, multi-step mutation tool with no output schema, the description covers everything an agent needs: what gets destroyed, reversibility, permission/auth requirements, and the staging/approval protocol including the PIN-safety rule. Nothing material is missing.

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 description coverage is 100%, so all three parameters (mailbox, provider, workspace) are already documented in the schema, including the conditional 'only needed when...' guidance. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 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 a specific verb+resource (disconnect a mailbox from a workspace) and immediately names the concrete effects: revokes the stored provider grant and deletes stored tokens. It is the only disconnect-style tool among the siblings, and the scope ('workspace you own') makes it unambiguous.

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?

Gives clear context for use and prerequisites: owners only, OAuth sign-in (no API keys), and the fact that the mailbox can be reconnected later from the dashboard. It does not explicitly name an alternative tool to compare against, but no close sibling alternative exists in the list.

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

All Higgs Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources