Skip to main content
Glama

Create Google Classroom assignment

create_google_classroom_assignment

Create an assignment in Google Classroom with an Educaplay activity, in one of the Classroom courses of the user. It does exactly what sharing the activity to Google Classroom from the Educaplay website does: Educaplay creates the assignment, so the grade of each student reaches Classroom when they finish the game. As on the website, the activity can be one of the user's or one by another author. Call it only when the user asks to send or assign an activity to Google Classroom. Without course_id it creates nothing and returns the courses of the Google account connected to Educaplay: ask which one when it is not clear, then call again with its course_id. Each assignment counts against the Google Classroom limit of the plan of the user, the same as on the website.

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": {
      "activity_id": "<activity_id>"
    },
    "name": "create_google_classroom_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNotrue saves the assignment as a draft that only the teachers of the course see until they publish it in Classroom; false or omitted publishes it to the students right away.
gradeNoWhich game becomes the grade in Classroom: "first" (the default, as on the website) the first one the student finishes, "best" the best of all of them.
course_idNoId of the Classroom course, from "courses" in a previous result of this tool. Omit it to get the courses.
activity_idYesId of the activity: from list_my_activities, or the number in the address of the activity when the user gives its link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true. The description adds genuinely non-obvious behavior: Educaplay creates and owns the assignment so grades flow back to Classroom on completion, the grade source can vary between first and best attempt, draft assignments stay hidden from students until teachers publish, and each assignment consumes the user's Classroom plan quota. It also discloses the side-effect of omitting course_id (creates nothing, returns a course list).

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?

Content is front-loaded on purpose and the action, the gating rule, and the course_id protocol all land early. There is mild redundancy in the repeated 'as on the website / the same as on the website' phrasing, but each sentence carries information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still tells the agent what the course_id-less invocation returns and that the activity can come from another author, covering both the creation flow and the discovery flow. For a 4-parameter write tool with openWorldHint, nothing an agent needs to invoke it correctly appears to be missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds two facts the schema does not: the course_id-less call both creates nothing and returns the account's courses (clarifying the discovery contract rather than just 'omit it to get the courses'), and that activity_id may refer to another author's activity, not only one from list_my_activities. It does not restate the draft/grade enum semantics, which the schema already handles well.

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 first sentence gives a specific verb and resource ('Create an assignment in Google Classroom with an Educaplay activity') and scopes it to one of the user's courses. It further distinguishes itself by equating the action to the website's share-to-Classroom flow, so an agent knows this is the Classroom-publishing path, not the generic activity tools in the sibling list.

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 states an explicit gating condition ('Call it only when the user asks to send or assign an activity to Google Classroom') and an explicit two-step protocol: call without course_id to enumerate courses, ask the user which one, then call again with course_id. That is a concrete when-to-use plus a when-NOT-to-proceed rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources