Skip to main content
Glama

Get Assignment

get_assignment
Read-only

Fetch a single Canvas assignment's instructions, rubric, due date, and submission status to clarify requirements and help the student plan their learning.

Instructions

Reads one assignment: instructions, rubric, due date, and the student's submission status. Use it to help the student understand what is being asked and what the rubric rewards. If the assignment is still open, help them plan and learn the underlying material; the work itself is theirs to write.

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>",
      "assignment_id": "<assignment_id>"
    },
    "name": "get_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
assignment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnlyHint=true and openWorldHint=true, so the burden is lighter. The description adds value beyond them by disclosing exactly what a read returns, including personal 'submission status' data, which tells the agent this surfaces a specific student's state rather than course metadata. It omits any note about permissions or failure modes when an id is wrong.

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?

Three sentences, front-loaded with the core capability, with no repetition of the name or annotations. The final sentence is an ethical guardrail rather than selection information, but it is short and materially shapes how the agent should use the result.

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 no output schema, the description carries the return-value burden and does partially meet it by naming the four content areas returned. However, for a two-parameter, zero-coverage schema it leaves the parameters wholly unexplained and says nothing about what happens when the assignment id does not exist or the student has no submission.

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 coverage is 0%, so the description ideally would explain course_id and assignment_id. It never mentions them. Mitigating factor: both are single integer identifiers whose names make their role self-evident, and the description implies the pair scopes the read to one student's assignment. Still, it adds no format or lookup guidance for the parameters themselves.

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 names a specific verb and scope ('Reads one assignment') and enumerates the payload ('instructions, rubric, due date, and the student's submission status'), which cleanly separates it from list-style siblings like get_upcoming_work or get_syllabus. It stops short of naming an explicit alternative, so it sits just below the top tier.

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

Usage Guidelines3/5

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

It gives intended usage ('Use it to help the student understand what is being asked and what the rubric rewards') plus a behavioral constraint about not doing the work for the student. That is pedagogical guidance rather than tool-selection guidance: no condition tells the agent when to prefer this over get_upcoming_work or get_feedback, and no prerequisites or exclusions are stated.

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