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

canvas-student-mcp

by xmike04
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List my groups

canvas_list_groups
Read-only

List Canvas groups you belong to, including project teams, study groups, and sections, with member counts and associated courses.

Instructions

List the Canvas groups you belong to (project teams, study groups, sections) with member counts and their course.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description's role is reduced. It adds the scope detail (user's groups, not all groups) but doesn't mention pagination, sorting, or any behavioral traits beyond the annotations.

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?

A single, concise sentence that front-loads the key information with zero waste.

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?

For a simple, parameterless, read-only tool with complete annotations, the description is sufficient. No output schema exists but the return values are implied. Could mention if results are filtered by user (already implied by 'you belong to').

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

Parameters4/5

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

Schema coverage is 100% with zero parameters, so there is nothing to add. Baseline 3 plus 1 for complete clarity.

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 uses a specific verb ('List') and resource ('Canvas groups'), and clarifies the scope ('you belong to') and content ('project teams, study groups, sections') with member counts and course. It clearly distinguishes from siblings which list different entities (courses, assignments, etc.).

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?

Implied usage is clear but no guidance on when not to use it or alternatives. With many siblings, explicit differentiation would help but the scope note partially addresses this.

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