Skip to main content
Glama
Sign In
Canvas MCP

Canvas MCP

by duggsha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_modules

Read-onlyIdempotent

Read Canvas course modules, prerequisites, and availability by course ID to review course structure and access.

Instructions

Read course modules, prerequisites and availability.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that results include prerequisites and availability; it says nothing about pagination or result limits despite the page parameter.

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 zero wasted words. It is efficient, though the brevity borders on under-specification rather than genuine conciseness.

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?

For a two-parameter read tool with no output schema and 0% schema coverage, the description should explain the ID requirement and pagination behavior. Neither is addressed, so the agent lacks enough to call it confidently beyond the bare minimum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so nothing documents courseId (a required constrained ID) or page (pagination with a 10000 max). The description mentions neither parameter, leaving the agent no meaning beyond the raw schema names.

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?

States a specific verb (Read) and resource (course modules) plus the informational payload it returns (prerequisites and availability). It does not explicitly distinguish itself from the close sibling list_module_items, so it falls short of a 5.

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?

No guidance on when to use this versus list_module_items, list_courses, or get_study_overview, and no prerequisites or exclusions mentioned. The agent must infer the applicable scenario from the name 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