Canvas MCP

get-study-progress

Track your study progress per course, including modules viewed, assignments completed, and grade status. Optionally filter by a specific course ID.

Instructions

Bekijk jouw studievoortgang per vak: hoeveel modules bekeken, opdrachten gedaan, cijfer status

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-study-progress"
  }
}

Input Schema

Name	Required	Description	Default
`courseId`	No	Optioneel: specifiek vak ID. Zonder ID worden alle vakken getoond

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention that the tool is read-only, requires authentication, or any side effects. It only describes the displayed information, leaving safety and permission requirements unaddressed.

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?

The description is a single sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded and every part adds value.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the key data returned (modules, assignments, grade status). It could mention prerequisites like authentication or enrollment, but overall it is sufficient for an agent to decide usage.

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?

The input schema has 100% coverage with a clear description for the single optional parameter 'courseId'. The tool description does not add further parameter meaning, so the baseline score of 3 is appropriate.

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 tool's purpose: viewing study progress per course, including modules viewed, assignments done, and grade status. It uses a specific verb ('Bekijk') and resource ('studievoortgang per vak'), distinguishing it from sibling tools like get-my-grades or get-module-content.

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?

The description implicitly suggests usage for per-course progress review, but lacks explicit guidance on when to use this tool versus alternatives such as get-my-grades for grade-only data. No exclusions or when-not-to-use instructions are provided.

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