Skip to main content
Glama
Sign In
quercus-mcp

quercus-mcp

by lance-lii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get grades for a course

get_course_grades

Fetches the user's grades and enrollment info for a specified course in Quercus/Canvas, enabling quick checks of academic status.

Instructions

Get the current user's grades/enrollment info for a specific 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": "get_course_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

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?

No annotations are provided, so the description carries the full behavioral burden. It implies a read of the calling user's own data, but says nothing about permissions, whether enrollment info is always present, error behavior for invalid courses, or the shape of the result.

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 tight sentence with the resource and scope front-loaded. Efficient, though it is arguably under-specified rather than optimally concise.

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?

For a read tool with no annotations and no output schema, the description should convey at least the return shape (grades vs. enrollment fields) and course_id format. It leaves both unresolved, so an agent cannot fully predict the response.

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 course_id parameter is a bare string with no format, example, or source hint in either the schema or the description. The description only implies the parameter is course-scoped, adding no real semantic value.

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?

States a specific verb (get) and resource (current user's grades/enrollment info) scoped to a specific course. It is distinguishable from siblings like list_all_grades, though the description never explicitly names that sibling to sharpen the contrast.

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?

No guidance on when to use this over list_all_grades or the other list_* siblings, and no stated prerequisites. The agent must infer that this is the per-course variant of a broader grades listing.

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