get_unread_discussion_countRetrieve unread discussion entry counts for each topic in a Canvas course to track new replies without reading every thread.
Get the unread entry count for each discussion topic in a course. Read-only and cheap. Use get_full_topic_view to read a topic.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | Canvas course ID, a numeric string such as "12345". Get it from list_courses. |
Changes observed during successful MCP inspections.
v1.0.2Input schema / properties / course_id / descriptionPrevious value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only 'cheap' as extra behavioral context and says nothing about return shape or cost specifics; with annotations doing the heavy lifting, a 3 is appropriate.
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?
Three short sentences, front-loaded with the core action, then a cost note, then the alternative routing. Nothing is wasted.
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 simple, annotated read-only count tool with a fully documented single parameter, the definition is essentially complete. It could mention that the return is a per-topic count map, but no output schema exists and the description already conveys the shape.
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?
There is one parameter with 100% schema coverage, and the schema already documents course_id including how to obtain it. The description adds no parameter-specific meaning beyond the schema, 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?
States a specific verb (get), resource (unread entry count), and scope (each discussion topic in a course). The agent can tell it apart from reading tools because the description names get_full_topic_view for reading a topic.
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?
Gives clear context (unread counts per discussion) and points to get_full_topic_view as the alternative for reading content. It does not address other count-related siblings like get_all_unread, but the usage boundary is clear enough for invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.