get_course_activity_streamGet a summary of recent activity in a course. Returns counts of recent events grouped by type (submissions, discussions, announcements, etc.).
Get a summary of recent activity in a course. Returns counts of recent events grouped by type (submissions, discussions, announcements, etc.).
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | The Canvas course ID |
Changes observed during successful MCP inspections.
v1.18.15Input schema / properties / course_id / anyOfAdded value: +[
+ {
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "type": "integer"
+ },
+ {
+ "pattern": "^[1-9][0-9]{0,18}$",
+ "type": "string"
+ }
+]Input schema / properties / course_id / typeRemoved value: -"number"v1.18.11Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and open-world behavior. The description adds output-level behavior beyond annotations: it discloses that the result is an aggregate summary (counts grouped by type) and gives example event types, which is useful given there is no output schema. It stops short of defining the 'recent' window or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action and followed by the return shape. Every sentence earns its place with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only tool with annotations and full schema coverage, the description covers both purpose and return content. The main missing piece is a definition of the 'recent' time window, and no output schema exists to compensate for that gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the sole parameter course_id is documented in the schema as 'The Canvas course ID'. The description adds no syntax, format, or constraint details beyond what the schema already provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ('Get a summary of recent activity in a course') and states the return shape (counts grouped by event type). It differentiates implicitly from get_my_activity_stream by scoping to a course, but does not name or rule out sibling analytics/activity tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use statement, no conditions for selecting this over get_course_analytics, get_student_analytics, or the other activity-stream siblings. Usage must be inferred entirely from the purpose sentence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.