Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Group Files

list_group_files
Read-onlyIdempotent

List files shared in a group workspace, including names, sizes, and IDs, to review available resources; then use download_file to save a specific file.

Instructions

List files shared in a group workspace with names, sizes and IDs. Read-only. Save one with download_file.

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": {
      "group_id": "<group_id>"
    },
    "name": "list_group_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
group_idYesStudent group ID (numeric string). Get it from list_my_groups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changedv1.1.3
    • changedInput schema / properties / group_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Student group ID (numeric string). Get it from list_my_groups."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' in the description is redundant. What it does add is the shape of the result (names, sizes, IDs), which helps since there is no output schema. It says nothing about permissions or pagination behaviour beyond the schema's own page/limit notes.

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?

Three short, front-loaded sentences with no filler: purpose and returned fields first, then the safety trait, then the next-step tool. Nothing is wasted.

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?

A simple, read-only listing tool with fully described parameters and annotations that carry the safety profile, so the description is nearly complete; it also compensates for the missing output schema by naming returned fields. Only the hand-off to download_file is spelled out, but extra operational detail is unnecessary here.

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?

Schema description coverage is 100%: group_id, page and limit are each documented in-schema, including where to obtain group_id ('from list_my_groups'). The description adds no parameter-level detail beyond the group-workspace framing, so the baseline 3 applies.

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?

States a specific verb and resource ('List files') plus a scoping qualifier ('shared in a group workspace') and the key fields returned (names, sizes, IDs). The group-workspace scope lets an agent separate it from list_course_files and list_my_files without opening a schema.

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?

The group-workspace scoping implies when to use it, and 'Save one with download_file' routes the agent to the correct follow-up tool. It stops short of naming when NOT to use it (e.g. personal or course files), so it is clear context without explicit exclusions.

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