Skip to main content
Glama

sign_in

Authenticate with Google Chat or renew an expired session by first trying a silent browser-profile refresh, then opening Chrome for manual sign-in (waits up to 10 minutes).

Instructions

Sign in to Google Chat or refresh an expired session. Tries a silent refresh from the saved browser profile first; if that fails, opens a Chrome window for the user to sign in (waits up to 10 minutes). Call this when other tools report the user is not signed in or the session expired.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does it well: it discloses the internal escalation strategy (silent refresh from the saved browser profile, then a visible Chrome window), the blocking wait of up to 10 minutes, and the implicit requirement for interactive user action. It stops short of saying what a failure looks like or whether the call returns before the user finishes.

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?

Three short sentences: what it is, how it behaves, when to call it. The escalation and timing details are packed into one clause each, and the trigger condition is placed last where the agent looks for routing guidance. No filler.

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

Completeness4/5

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

For a zero-parameter authentication tool with an output schema already documenting return values, the description covers the essentials: dual-mode auth, the visible-window fallback, and the long blocking window. A note on what happens if the 10-minute wait expires would close the remaining gap.

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 takes zero parameters, so there is nothing to disambiguate; the baseline applies. The description gains nothing here but also leaves no confusion.

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 and resource ("Sign in to Google Chat") plus a second concrete outcome ("refresh an expired session"). Nothing in the sibling list (lists, reads, searches) overlaps with this, so the agent can distinguish it instantly.

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 an explicit triggering condition: "Call this when other tools report the user is not signed in or the session expired." That is a clear when-to-use rule tied to observable signals. It doesn't state when-not to call (e.g., don't call preemptively on a healthy session), which is the only gap.

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