classroom-mcp-server

Turn In Assignment

classroom_turn_in_submission

Submit a student assignment to the teacher, changing its state from CREATED or NEW to turned in. Use to hand in work when the submission is ready.

Instructions

Turn in (submit) a student assignment submission. This hands the work to the teacher and is the equivalent of clicking "Turn in". State must currently be CREATED or NEW.

Args:

course_id, coursework_id, submission_id (strings)

Returns: Confirmation. NOTE: This changes submission state and is not trivially reversible (use classroom_reclaim_submission to pull it back if still allowed).

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": {
      "course_id": "<course_id>",
      "coursework_id": "<coursework_id>",
      "submission_id": "<submission_id>"
    },
    "name": "classroom_turn_in_submission"
  }
}

Input Schema

Name	Required	Description
`course_id`	Yes
`coursework_id`	Yes
`submission_id`	Yes	From classroom_list_submissions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

It discloses that the tool mutates submission state, is not trivially reversible, and names the reclaim tool for undoing it. This adds meaningful context beyond the annotations, which only indicate readOnlyHint=false and idempotentHint=false.

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?

The description is compact and front-loads the core purpose, then adds state requirements, return info, and reversal guidance in a structured way. The Args list is somewhat redundant with the schema, but the overall length is appropriate.

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 provides the critical state precondition, the mutation behavior, and the reversal path, which are essential for correct use. Missing details like error behavior for invalid states or fuller parameter semantics leave minor gaps, but the tool is otherwise well-specified.

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%, with only submission_id having a description. The description merely lists param names and types but does not explain course_id or coursework_id beyond what the schema already shows, failing to compensate for the coverage gap.

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 clearly states the action: turning in/submitting a student assignment submission, with the concrete analogy of clicking 'Turn in'. It names the required state (CREATED or NEW) and is distinct from sibling tools like listing or reclaiming submissions.

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 conveys when to use this tool: to submit work to the teacher, and only when state is CREATED or NEW. It also explicitly points to the reclaim sibling for reversing the action if allowed, giving useful guidance for choosing alternatives.

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

Deploy Server