Skip to main content
Glama

Read Canvas announcements

canvas_announcements
Read-onlyIdempotent

Retrieve recent announcements from your Canvas classes, newest first. Filter by course or set a day range to view only relevant updates; read-only.

Instructions

Announcements from the user's Canvas classes in the last days days, newest first. course narrows it to one class (a course number or part of its name); leave it empty for every class. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
courseNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the closing 'Read-only' is largely redundant. The description does add useful behavior: results are ordered newest first and the default scope spans every class. It says nothing about result caps, pagination, or how many announcements per class are returned.

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?

Two tight sentences, front-loaded with the resource and time scope, followed by the filtering option. The only waste is the trailing 'Read-only', which restates the readOnlyHint annotation.

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?

An output schema exists so return values need not be described, and with only two optional parameters the tool is simple. The remaining gap is operational detail such as result limits or pagination, which an agent would want before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter meaning, and it largely does: `days` is the lookback window and `course` accepts a course number or partial name, with empty meaning all classes. It omits the concrete default of 14 days, but otherwise explains both parameters better than the bare 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?

States a specific resource (Canvas announcements), source (the user's classes), and a time scope (`days`), which is enough to distinguish it from siblings like canvas_assignment or canvas_page. It does not explicitly contrast with any named sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the parameter notes: use `course` to narrow to one class, leave empty for all. There is no guidance on when to prefer this over related read tools such as canvas_search or catch_up, and no stated exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.