Skip to main content
Glama

classroom_create_assignment

Creates Google Classroom assignments, short-answer questions, or multiple-choice questions with optional attachments, due dates, and topics.

Instructions

Create an assignment, a short-answer question or a multiple-choice question (one question with choices) with optional attachments, due date, and topic.

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>",
      "title": "<title>"
    },
    "name": "classroom_create_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoDRAFT
titleYes
choicesNoAnswer options; required for MULTIPLE_CHOICE_QUESTION only
dueDateNoYYYY-MM-DD in the local time zone of this computer
dueTimeNoHH:MM in local time (defaults to 23:59 if dueDate is set); converted to UTC automatically
topicIdNo
courseIdYes
workTypeNoASSIGNMENT
maxPointsNo
attachmentsNo
descriptionNo
scheduledTimeNoRFC 3339 timestamp for scheduled publication

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.1.0
    • addedInput schema / properties / choices
      Added value: +{
      +  "description": "Answer options; required for MULTIPLE_CHOICE_QUESTION only",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "minItems": 2,
      +  "type": "array"
      +}
    • changedInput schema / properties / workType / enum
      Previous value: -[
      -  "ASSIGNMENT",
      -  "SHORT_ANSWER_QUESTION"
      -]New value: +[
      +  "ASSIGNMENT",
      +  "SHORT_ANSWER_QUESTION",
      +  "MULTIPLE_CHOICE_QUESTION"
      +]
  2. First observedv3.0.0-beta.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare a write operation (readOnlyHint=false) with external visibility (openWorldHint=true), but the description adds no behavioral detail beyond what the annotations imply. It does not mention that state defaults to DRAFT, what happens when an assignment is PUBLISHED (student visibility/notifications), or how scheduling interacts with due dates.

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?

A single front-loaded sentence that wastes no words and puts the resource types first. It is compact, though a second sentence of guidance would have earned its place for a 12-parameter tool.

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?

With 12 parameters, no output schema, and sparse description coverage, the definition leaves significant gaps, especially around defaults and mutation consequences. What is present is accurate but thin for a tool of this complexity.

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 only 33%, so the description should compensate, yet it only names attachments, due date, and topic without explaining formats or defaults. Key semantics such as workType default, DRAFT default, choices only applying to MULTIPLE_CHOICE_QUESTION, and scheduledTime versus dueTime are left to partial schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Create) and resource (assignment / short-answer question / multiple-choice question), and clarifies that multiple-choice means one question with choices. It does not explicitly distinguish itself from classroom_create_material, but the enumeration of the three work types makes the scope clear.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus classroom_create_material, classroom_create_topic, or classroom_patch_assignment, and no prerequisites such as needing an existing course or teacher permissions. The agent must infer usage entirely from the name and schema.

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