Skip to main content
Glama

Add Favorite Course

add_favorite_course
Idempotent

Star a Canvas course as a favorite to display it on your dashboard, affecting only your own view. Use remove_favorite_course to reverse it.

Instructions

Star a course as a favorite so it shows on your Canvas dashboard. Only affects your own view. Reverse with remove_favorite_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": "add_favorite_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
  2. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare mutation, idempotency, and non-destructiveness; the description adds genuinely new context — the effect is scoped to the caller's own view and it is reversible via remove_favorite_course. It does not state what happens if the course is already favorited (idempotency) or whether the course must be enrolled/visible, leaving small gaps.

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?

Three short sentences with zero filler; the primary action and its effect come first, scoping second, and the reversal pointer last. Every sentence earns its place.

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

Completeness5/5

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

For a one-parameter, non-destructive, idempotent mutation with full schema documentation and no output schema, nothing an agent needs to invoke it correctly is missing. Scope and reversibility are both covered.

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?

The single course_id parameter is fully documented in the schema, including format and how to obtain it via list_courses, so schema coverage is 100% and the description needn't repeat it. Baseline 3 applies since the description adds no parameter meaning beyond the schema.

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?

States a specific verb (star as favorite) and resource (a course), plus the concrete effect: it shows on the Canvas dashboard. It also names the sibling that undoes it, so an agent can distinguish it from list_favorite_courses and remove_favorite_course without opening a schema.

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?

Gives clear context for use (marking a course to surface on the dashboard) and explicitly points to remove_favorite_course as the reverse operation. It lacks an explicit 'do not use if you want to just view favorites' clause, but the alternative is still implied by the named sibling.

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