Skip to main content
Glama

Read Course Page

read_course_page
Read-only

Reads a Canvas course page's text so a student can be quizzed on its ideas, supporting active recall instead of passive summary.

Instructions

Reads the text of a Canvas course page. When studying from it, quiz the student on the ideas rather than summarizing the page for them: recalling is what builds memory.

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_id": "<course_id>",
      "page_url": "<page_url>"
    },
    "name": "read_course_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_urlYesThe page_url value from list_course_materials
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the return is the page's text, which is useful and consistent with the read-only hint, but it says nothing about truncation, size limits, auth requirements, or whether non-text elements are included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core purpose front-loaded, so it is compact. However, the second sentence is behavioral instruction to the agent about study technique rather than tool description, so it does not earn its place in a tool definition even though it is brief.

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?

For a simple two-parameter read tool whose annotations already signal read-only and open-world access, most of what an agent needs is present. Gaps remain around the course_id parameter and around the shape or limits of the returned text, which the description never addresses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: page_url is documented ('The page_url value from list_course_materials') but course_id has no schema description, and the tool description supplies no parameter meaning at all. With half the parameters undocumented in structured fields, the description should have compensated and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Reads the text of a Canvas course page.' An agent can tell it fetches page body text rather than materials metadata or assignments, since the sibling names imply those other resources. It stops short of explicitly contrasting itself with any sibling such as list_course_materials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no explicit alternative named. The only usage-adjacent text is a pedagogical directive about quizzing the student rather than summarizing, which concerns how to handle the content after reading, not which tool to select.

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