Skip to main content
Glama
Sign In
quercus-mcp

quercus-mcp

by lance-lii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List courses

list_courses

Retrieve a user's Quercus courses from Canvas LMS, optionally filtered by enrollment state such as active, completed, invited, or all.

Instructions

List the user's Quercus courses.

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

Input Schema

NameRequiredDescriptionDefault
enrollment_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 behavioral burden, yet it only implies read-only via 'List'. It discloses nothing about auth requirements, pagination, rate limits, or whether inactive/completed courses are included by default.

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 no filler. It is appropriately sized, though its brevity comes at the cost of the missing detail noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and one undocumented filtering parameter, the description is too thin to let an agent invoke this correctly — it cannot know the default enrollment filter or the shape of the returned course list.

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 description coverage is 0% and the single parameter enrollment_state (enum: active/completed/invited_or_pending/all) is never mentioned. The description does not explain the filter, its default, or its impact on results, leaving a documented-in-name-only parameter.

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 states a specific verb ('List') and resource ('the user's Quercus courses'), so the agent knows exactly what it returns. It does not, however, distinguish itself from sibling list tools such as list_assignments or list_all_grades beyond the resource noun.

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 guidance on when to call this versus the many sibling list_* tools, no prerequisites, and no exclusions. The agent must infer usage entirely from the resource name.

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