get_course_bundleFetch an entire Canvas course's folders, files, modules, and assignments in one request, eliminating the need for multiple API calls.
Fetch course, folders, files, modules, and assignments in one call.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | Canvas course ID |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states that it fetches multiple resource types, but doesn't disclose any behavioral details such as read-only nature, potential pagination, size limits, or response structure. It adds little beyond what the name implies.
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?
The description is a single, clear sentence that front-loads the action and resource list. Every word earns its place with no redundancy or fluff.
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 single-parameter tool, the description adequately indicates what is fetched. It doesn't explain return format or pagination, but given the simplicity and no output schema, it is sufficient for an agent to call it correctly. A bit more detail on the aggregated structure would be nice, but it's not essential.
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 a single parameter, course_id, and the schema description already explains it as 'Canvas course ID' (100% coverage). The description adds no further meaning or syntax details, so it meets the baseline for high schema coverage.
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 states a specific action (fetch) and a specific resource set (course, folders, files, modules, assignments) in one call. It clearly distinguishes from sibling list tools by indicating a bundled fetch, though it doesn't name any sibling explicitly.
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?
The phrase 'in one call' implies this is an alternative to calling multiple list tools individually. However, it doesn't explicitly state when to prefer this over the granular list tools, nor any exclusions or limitations. The context is clear but lacks explicit routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.