Skip to main content
Glama

get_assignments

Retrieve assignments for a specific Canvas course by providing its course ID, so you can review coursework and due dates.

Instructions

Get assignments for a specific Canvas course

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

Input Schema

NameRequiredDescriptionDefault
course_idYesCanvas course ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Get' implies a read, but nothing is said about pagination, whether submissions or due dates are included, permission requirements, or ordering.

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 with no wasted wording. It is efficiently written, though perhaps too terse to carry much structure.

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?

For a simple one-parameter read tool with no annotations or output schema, the description covers the core action but omits return shape, volume/pagination expectations, and sibling differentiation. Adequate as a minimum, but an agent would need the schema and trial calls to use it confidently.

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 description coverage is 100% with a single required course_id already documented as 'Canvas course ID', so the schema does the heavy lifting. The description reinforces that the parameter selects a specific course but adds no format or lookup detail beyond that.

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 (Get) and resource (assignments) scoped to a Canvas course, so an agent can tell what it retrieves. It stops short of distinguishing the tool from the sibling get_upcoming_assignments, leaving ambiguity about which one to pick.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'for a specific Canvas course' hints at the required context but does not say how this differs from get_upcoming_assignments or get_calendar_events.

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