Skip to main content
Glama
Sign In
google-classroom-mcp

google-classroom-mcp

by alanmagno1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_courses

Retrieve the list of Google Classroom courses you are enrolled in, specifying an account and including archived courses when needed.

Instructions

Cursos de Classroom en los que estás inscrito como alumno. Sin account recorre todas las cuentas configuradas.

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

Input Schema

NameRequiredDescriptionDefault
accountNo
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. It does disclose the multi-account traversal behavior and the student-enrollment scope. However, it does not mention pagination, output format, permissions, or whether archived courses are handled beyond the include_archived parameter.

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?

The description is only two short Spanish sentences with no filler or redundant phrases. It is front-loaded with the main purpose and then adds the key account-related nuance.

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?

For a simple list tool with two optional parameters and no annotations or output schema, the description covers the core behavior and account aggregation, but it leaves include_archived and the expected return shape unstated. It is adequate but has clear gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It meaningfully explains the account parameter (when omitted, it iterates all configured accounts), but it provides no additional semantics for include_archived at all, leaving that parameter to be understood only from its name and schema default.

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?

The description clearly states the tool's resource and scope: Classroom courses in which the user is enrolled as a student. It also distinguishes the tool from siblings such as get_course_contents or get_assignment by emphasizing an aggregate course list rather than a single item.

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?

The description provides clear context about when to use it (courses where the user is a student) and the behavior when account is not provided (recorre todas las cuentas configuradas). It does not explicitly name alternatives or exclusions, but the context is enough for basic tool selection.

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