Skip to main content
Glama

classroom_connect

Connect or reconnect Google Classroom without a terminal: it uses the credentials file in Downloads and opens Google sign-in in your browser for first-time setup or expired sessions.

Instructions

Connect or reconnect Google Classroom without a terminal: picks up the credentials file from the Downloads folder if needed and opens Google sign-in in the teacher's browser. Use it for first-time setup and whenever the sign-in has 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": "classroom_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only tell the agent this is not read-only and touches the open world; the description adds real behavioral context — it reads a credentials file from the Downloads folder and launches an interactive browser sign-in, which implies a human must be present. It does not say where the credentials file must come from or what happens if it is missing, which is the main residual gap.

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?

Two sentences, zero filler, and the mechanism is front-loaded ahead of the usage conditions. The 'without a terminal' framing immediately sets expectations for the agent and the user.

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, no-output-schema setup tool, the definition covers what it does, how it does it, and when to invoke it — enough to call it correctly. It could be slightly more complete by noting prerequisites for the credentials file or any expected return/failure signal.

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 no argument semantics to explain and the baseline of 4 applies. The description's mention of the Downloads folder correctly signals that no path argument is needed.

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 (connect/reconnect) and resource (Google Classroom), plus the mechanism (credentials file from Downloads, opens Google sign-in in the teacher's browser). This is unmistakably distinct from the CRUD/list siblings, which all operate on courses, posts, and materials rather than on the auth/session itself.

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 explicit trigger conditions: 'first-time setup' and 'whenever the sign-in has expired.' That covers the realistic when-to-use cases without the agent having to infer them. It stops short of naming when-not-to-use (e.g. if already connected) or an alternative recovery path if sign-in fails.

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