Skip to main content
Glama
Sign In
quercus-mcp

quercus-mcp

by lance-lii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List course files

list_files

Retrieve files from a Quercus course by course ID, enabling users to browse and access available course materials through read-only Canvas LMS integration.

Instructions

List files available in a Quercus course.

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

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 behavioral burden, and it discloses almost nothing: no pagination behavior, no permission/enrollment requirements, no statement about whether hidden or unpublished files are included, and no indication of what each entry contains. "Available in a Quercus course" is the only scope hint.

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 short, front-loaded sentence with no wasted words. It is efficiently structured, though its brevity edges toward under-specification rather than ideal conciseness.

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 list tool with no output schema, the definition is minimally viable, but it omits return shape, pagination, and the relationship to get_file_download_url. Those gaps are the kind an agent would need to call this correctly in a multi-step workflow.

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 there is one required parameter (course_id). The phrase "in a Quercus course" loosely implies course_id identifies the course, but adds nothing beyond what the parameter name already conveys, so it fails to compensate for the undocumented 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 states a specific verb+resource ("List files") scoped to a Quercus course, which clearly separates it from list_assignments, list_announcements, and list_courses. It does not, however, explicitly name or distinguish itself from the closely-related get_file_download_url sibling.

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 the natural alternative get_file_download_url for actually retrieving file content. An agent must infer everything about when this list tool is appropriate.

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