Skip to main content
Glama

Read a Canvas page

canvas_page
Read-onlyIdempotent

Read the complete content of a single Canvas course page by title, partial title, or page ID.

Instructions

Read one Canvas page in full. page is its title (or part of it) or the page id from canvas_pages. 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>",
      "page": "<page>"
    },
    "name": "canvas_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing 'Read-only.' merely repeats structured data rather than adding to it. The description adds no behavior beyond that: it says nothing about partial-title matching rules, multiple-match resolution, or not-found handling, which are the real behavioral unknowns for a lookup by fuzzy title.

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 sentences ordered well: action first, then the ambiguous parameter's accepted forms, then the safety note. Nothing is padded, though the final 'Read-only.' sentence duplicates an annotation and could instead have spent those words on 'course'.

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 explained, and the destructive/idempotency profile is covered by annotations. The remaining shortfall is the undocumented 'course' parameter, which is required yet never referenced anywhere in the description or schema.

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?

Schema description coverage is 0%, so the description must carry all parameter meaning. It does well for 'page' by stating it accepts a title, a partial title, or a page id sourced from canvas_pages — meaningful beyond the bare 'Page' title in the schema — but the required 'course' parameter is never mentioned, leaving one of two required inputs entirely undefined.

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?

The description names a specific verb and resource — 'Read one Canvas page in full' — and the singular 'one ... page' plus 'in full' implicitly separates it from the sibling listing tool canvas_pages, which it explicitly references as the source of page ids. An agent can tell what this does without opening the schema.

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: the reference to 'the page id from canvas_pages' hints that canvas_pages is the discovery step before this fetch, but the description never states when to use this versus canvas_pages or canvas_search, nor what happens when a page title is ambiguous or missing.

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