Skip to main content
Glama
Sign In
Neuro-CanvasLMS

Neuro-CanvasLMS

by BloodyReginaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

canvas_courses

Read-onlyIdempotent

List enrolled Canvas courses and return course IDs. Filter by active, completed, or invited/pending enrollment state for current, past, or invitation courses.

Instructions

List enrolled courses; use returned course IDs. Current courses by default; enrollment_state "completed" lists past (concluded) courses, "invited_or_pending" lists course invitations.

Input Schema

NameRequiredDescriptionDefault
rawNotrue: Canvas's unmodified JSON (UTC times, HTML).
pageNoPage to fetch: a number, or the next_page value returned by the previous call.
enrollment_stateNoWhich courses: active (default, current), completed (past) or invited_or_pending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent operation. The description adds useful behavioral context beyond that: current courses are returned by default, completed means past/concluded courses, and invited_or_pending covers invitations.

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?

The description is concise and front-loaded, with the default behavior stated before the alternate modes. Every phrase contributes directly to correct invocation.

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 list tool with fully documented parameters and annotations covering safety, this is nearly complete. It could mention pagination or the list-return shape, but those details are not essential and the page parameter is fully documented in schema.

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%, so the parameters are already well documented. The description adds some meaning around enrollment_state defaults and interpretation, but most parameter semantics are already supplied by the schema.

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?

The description gives a specific verb and resource: list enrolled courses. It is clearly distinct from the singular canvas_course tool by implication, but it does not explicitly name sibling alternatives such as canvas_enrollments.

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?

It clearly explains the default scope (current courses) and the two alternative enrollment_state modes. It lacks explicit guidance on when to prefer canvas_enrollments or canvas_course instead, but the usage context is otherwise clear.

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