Skip to main content
Glama
Sign In
mcp-canvas-utem

mcp-canvas-utem

by k0ngan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

canvas_export_course_sources

Exports a Canvas course's original instructions, pages, modules, links, and attachments as JSON to an output folder, preserving course source content for backup or migration.

Instructions

Guarda las instrucciones originales, páginas, módulos, enlaces y adjuntos de un curso como JSON en la carpeta de salida.

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": "canvas_export_course_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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. It does disclose the key side effect (writes JSON into an output folder), but says nothing about whether existing files are overwritten, where the output folder is, what access/enrollment is required for the course, or whether the operation is otherwise read-only on the LMS side.

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?

One compact sentence that front-loads the verb and enumerates the exported content types. Nothing is wasted, though the enumeration is long enough that it could have been split to also carry usage or output-location detail.

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 export tool with no output schema and no annotations, the description covers what is produced and in what format, which is the essential part. It still omits where the output goes, file naming/overwrite behavior, and any course_id validity rules, leaving real gaps for an agent to guess at.

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 coverage is 0% and the single property course_id has no description, type explanation, or constraint note beyond integer/minimum 1. The description only implies that the tool acts on 'a course', which is a marginal hint rather than real semantic detail (e.g., what counts as a valid course, whether it must be enrolled).

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 (guarda/save) and a concrete resource set — original instructions, pages, modules, links and attachments of a course — plus the output form (JSON in the output folder). This clearly distinguishes it from file-download or sync siblings by intent, though no sibling is named explicitly.

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 or when-not-to-use guidance and no mention of alternatives such as canvas_download_course_files or canvas_sync_course, which an agent could easily confuse with an export. Usage is only inferable from the stated purpose.

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