Skip to main content
Glama

List Canvas pages

canvas_pages
Read-onlyIdempotent

List pages in a Canvas course to find course info, policies, and handouts, then read a specific page.

Instructions

The list of pages in a Canvas class (course info, policies, handouts). Read one with canvas_page. Read-only.

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": "<course>"
    },
    "name": "canvas_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description merely restates structured data. Beyond that it only hints at the nature of the content returned, adding no permission requirements, ordering, or truncation behavior that the annotations don't already carry.

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?

Three short clauses, front-loaded with the resource and scope, with the sibling pointer placed after the core statement. The only waste is 'Read-only', which duplicates the annotations instead of contributing new information.

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

Completeness3/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 the single-argument surface is small. What remains unaddressed is the format of the course identifier and whether the page list is complete or paginated, which leaves a real gap for an otherwise simple tool.

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?

With only one parameter, the schema coverage is 0% and the schema gives just 'course' as a bare string. The description partially compensates by framing course as the Canvas class the pages belong to, but it never says whether the value is a course ID, a name, or a code, which is the main ambiguity for this arg.

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 resource and scope (the list of pages inside a single Canvas class) and gives concrete examples of page kinds (course info, policies, handouts). It also names the sibling it is not ('Read one with canvas_page'), so an agent can separate listing from fetching a single page without opening either 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 a clear condition-driven route: use this for the list, use canvas_page for a single page. It does not cover edge cases such as what to do if no pages exist or whether the list is filtered, so it falls short of the explicit when/when-not guidance a 5 requires.

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