google-classroom-mcp

list_pending_assignments

Check which assignments are still pending across active Google Classroom courses, grouped by account and course and sorted by due date, including overdue work.

Instructions

Tareas que aún no has entregado (estado NEW, CREATED o RECLAIMED_BY_STUDENT), agrupadas por cuenta y curso y ordenadas por fecha límite. Sin account ni course_id revisa todos los cursos activos de todas las cuentas. Incluye si ya venció.

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

Input Schema

Name	Required	Description	Default
`account`	No
`course_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations present, the description carries the burden of behavioral disclosure. It reveals the status filter, grouping, ordering by deadline, and inclusion of overdue indicator. It does not mention pagination, rate limits, or authorization, but for a read-only list tool this is reasonable.

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 compact sentences deliver all essential information—what is listed, statuses included, grouping, sorting, and default scope—without redundantly repeating the schema.

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?

The description covers statuses, grouping, sorting, default behavior, and overdue flag. Since there is no output schema, an agent gets enough to call the tool correctly. Minor missing details (sort direction, pagination, return format) prevent a perfect score.

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 schema has no descriptions and only shows account/course_id as nullable strings. The description adds crucial semantics: omitting them means scanning all accounts/courses(), which is more than the bare schema provides. It stops short of explaining expected ID formats.

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 ('List'), names the exact resource ('pending assignments'), enumerates the included statuses (NEW, CREATED, RECLAIMED_BY_STUDENT), and specifies grouping and sorting. This clearly distinguishes it from siblings like list_courses or get_assignment.

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 explains the behavior when parameters are omitted ('Sin account ni course_id revisa todos los cursos activos de todas las cuentas'), giving a clear decision rule. It does not explicitly contrast with sibling tools, but the context makes the appropriate use obvious.

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

Deploy Server