Skip to main content
Glama

get_modules

Retrieve all modules for a specific Canvas course using its course ID. Helps organize and navigate course content.

Instructions

Get all modules 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_modules"
  }
}

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?

With no annotations, the description carries the full burden and discloses nothing beyond the basic operation. It doesn't say whether modules come back ordered, whether nested items are included, whether unpublished modules are returned, what permissions the token needs, or whether results are paginated.

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 filler; the risk here is under-specification rather than verbosity. Nothing in the wording is redundant.

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 one-parameter read tool with no output schema, the description is minimally sufficient to call it correctly. It stops short of telling the agent anything about the shape of the returned module list or pagination, which is the main remaining gap.

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?

There is a single parameter with 100% schema description coverage ('Canvas course ID'), so the schema already does the heavy lifting and the baseline is 3. The description adds no format or sourcing detail (e.g., how to obtain a course_id) beyond what the schema provides.

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 and resource (get all modules) scoped to a Canvas course, which is enough to distinguish it from siblings like get_assignments or get_quizzes that return other resource types. It doesn't explicitly name alternatives, but the resource noun does the differentiation work.

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 when-to-use guidance, no prerequisites, and no mention of when another tool would be a better fit. The sentence only restates what the tool returns, leaving the agent to infer that this is the tool for browsing course content structure.

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