Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Assignment Details

get_assignment_details
Read-only

Retrieve detailed information for a specific Canvas assignment using its course identifier and assignment ID, including due dates, availability windows, and timestamps.

Instructions

Get detailed information about a specific assignment.

Input Schema

NameRequiredDescriptionDefault
raw_datesNoAppend a JSON block with due_at, unlock_at, lock_at, updated_at, all_dates and checkpoint dates exactly as Canvas returns them (null stays null). Default False.
assignment_idYesCanvas assignment ID
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / raw_dates
      Added value: +{
+  "default": false,
+  "description": "Append a JSON block with due_at, unlock_at, lock_at,\nupdated_at, all_dates and checkpoint dates exactly as Canvas\nreturns them (null stays null). Default False.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  3. Changed9 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assignment_id / description
      Added value: +"Canvas assignment ID"
    • removedInput schema / properties / assignment_id / title
      Removed value: -"Assignment Id"
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • removedInput schema / title
      Removed value: -"get_assignment_detailsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_assignment_detailsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_assignment_detailsArguments"
  5. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds no behavioral context beyond that—it does not explain what 'detailed information' contains, whether the call is affected by permissions, or what the raw_dates flag changes. For a read-only tool with annotations, this is a minimal contribution.

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 a single sentence, front-loaded and free of filler. It is concise, though that conciseness comes at the cost of missing useful context rather than being optimally informative.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should explain what 'detailed information' entails (e.g., assignment metadata, due dates, submission types). It does not, and it also omits any differentiation from the many sibling assignment-related tools. For a tool in a crowded LMS namespace, this leaves key context absent.

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 course_identifier, assignment_id, and raw_dates all documented in the schema. The description adds no additional meaning or formatting guidance beyond that baseline, so it neither helps nor harms parameter selection.

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

Purpose3/5

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

The description states a specific verb and resource (get, assignment), but it essentially restates the title 'Get Assignment Details' without clarifying what 'detailed information' includes or how it differs from sibling tools like list_assignments, get_assignment_analytics, or get_my_assignment_scores. An agent can identify the resource but not the exact scope.

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 guidance on when to use this tool versus alternatives such as list_assignments or get_assignment_analytics, nor any mention of prerequisites or context. The agent must infer that this is a single-assignment retrieval tool from the required parameters alone.

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

Deploy Server

Other Tools