Canvas MCP

get-assignment-details

Retrieve assignment details including description, rubric, deadlines, and submission requirements by providing course and assignment IDs.

Instructions

Haal volledige details op van een opdracht: beschrijving, rubric, deadlines, submission requirements

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": {
      "courseId": "<courseId>",
      "assignmentId": "<assignmentId>"
    },
    "name": "get-assignment-details"
  }
}

Input Schema

Name	Required	Description	Default
`courseId`	Yes	Het ID van het vak
`assignmentId`	Yes	Het ID van de opdracht

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool as retrieving details but does not disclose any behavioral aspects such as access requirements, error behavior, or whether it modifies data. Minimal transparency beyond purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, focused sentence with no filler. Front-loaded with the main action and lists key outputs efficiently.

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?

Description mentions key output components (description, rubric, deadlines, submission requirements), providing useful context. Without an output schema, this helps agents understand what to expect. Could be more exhaustive but sufficient given sibling tools for specifics.

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?

Both parameters have descriptions in the schema (100% coverage), so the description adds no additional meaning. Baseline score of 3 is appropriate as schema already documents parameters.

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?

Description clearly states the tool retrieves full assignment details, listing specific components (description, rubric, deadlines, submission requirements). This distinguishes it from sibling tools like get-assignment-rubric or get-assignment-feedback.

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?

Description implies use when needing a comprehensive overview of an assignment, but does not explicitly state when to prefer this over sibling tools or exclude cases. The listing of included items provides implicit guidance.

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