google-classroom-mcp

Overview Schema Source Related Servers Discussions Admin

classroom_get_course

Read-only

Get full details of a specific Google Classroom course by providing its course ID. Access course information to manage topics, assignments, and materials.

Instructions

Get full details of a specific course by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "courseId": "<courseId>"
    },
    "name": "classroom_get_course"
  }
}

Input Schema

Name	Required	Description	Default
`courseId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0-beta.1Sep 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, so the description does not need to repeat that. However, the description adds no behavioral details beyond that, such as error behavior or what 'full details' includes.

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?

A single, front-loaded sentence with no filler. Every word adds meaning and the key distinction ('by ID') is included.

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 simple read-only getter with one required parameter and readOnlyHint=true, the description is largely sufficient. It explains what the tool returns ('full details') and the lookup method, though it does not describe error or not-found behavior.

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 0%, but the single parameter courseId is self-explanatory and the description reinforces it by saying the course is retrieved 'by ID'. No additional format, source, or usage semantic is provided, but none is strictly needed for this simple parameter.

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 uses a specific verb ('Get') and resource ('full details of a specific course'), and clarifies the selection mechanism ('by ID'). This clearly distinguishes it from list/search/update siblings.

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?

The 'by ID' phrasing implies the tool should be used when a course ID is already known, but there is no explicit guidance about when to prefer list_courses or search_courses instead. Usage context is implied rather than explicitly stated.

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