Skip to main content
Glama

classroom_get_overview

Read-only

Get a one-call planning summary across your Google Classroom courses: unpublished drafts, scheduled posts, and assignments due soon, so you can see pending work without listing each course.

Instructions

One-call planning summary across the courses the teacher teaches: unpublished drafts (count plus up to 20 per course), posts scheduled for later and assignments due in the coming days. Use it for questions like "what do I have pending this week?" instead of listing each course.

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_get_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdsNoLimit to these courses (default: every active course the teacher teaches, up to 30)
daysAheadNoHow far ahead to look for due dates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real behavioral detail beyond that by disclosing truncation ('up to 20 per course'), the default look-ahead of the coming days, and that only active teacher-owned courses are in scope. It does not say whether truncation is flagged in the output or how the aggregation behaves with large course sets, which is why it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns and followed by the usage trigger; there is no filler. The return-contents list is dense and slightly run-on, which keeps it from being maximally scannable.

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?

With no output schema, the description carries the burden of describing the return shape and does so by naming all three result categories plus the per-course cap. Remaining gaps are minor: it does not clarify what form 'posts scheduled for later' take or whether an empty/truncated result is distinguishable.

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 courseIds default/cap and daysAhead's 'how far ahead' are already documented; the baseline of 3 applies. The description reinforces the semantics by tying 'due in the coming days' to daysAhead and 'courses the teacher teaches' to the courseIds default, but adds no format or interaction detail beyond the schema.

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 states a concrete resource (a cross-course planning summary) and enumerates exactly what it returns: unpublished drafts with counts and up to 20 items per course, scheduled posts, and upcoming due assignments. The clause 'instead of listing each course' separates it from the per-course list siblings such as classroom_list_assignments, so an agent can choose it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use trigger ('what do I have pending this week?') and an explicit alternative to avoid ('listing each course'). The scope statement 'across the courses the teacher teaches' also implies the boundary condition, so the routing decision is fully specified.

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