Skip to main content
Glama

Read a Canvas assignment

canvas_assignment
Read-onlyIdempotent

Retrieve full details for a Canvas assignment: instructions, rubric, due date, points, submission method, and submitted status. Read-only; never submits anything.

Instructions

The full details of one Canvas assignment: instructions, rubric (if the teacher added one), due date in the user's time zone, points, how it's submitted, and whether they've already submitted it. assignment is its name (or part of it) or its id. Read-only: never submit anything for the user.

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>",
      "assignment": "<assignment>"
    },
    "name": "canvas_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes
assignmentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 safety profile is covered. The description still adds real context beyond them: due dates are rendered in the user's timezone, the rubric may be absent, and the submission status reflects the user's own submissions. It does not discuss behavior for ambiguous names or non-existent assignments.

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

Conciseness5/5

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

Two sentences, front-loaded with the payload the caller receives, followed by the parameter clarification on the one ambiguous field. The read-only guardrail is short and earns its place as a hard constraint on agent behavior. No filler or restatement of the title.

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 the description needn't explain return values in detail, and its summary of contents is a helpful preview rather than a burden. For a two-parameter read tool the coverage is nearly complete; the only real gap is the unexplained `course` parameter and no guidance on disambiguating partial-name matches.

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 parameter meaning. It does clarify one of two parameters well ("`assignment` is its name (or part of it) or its id"), which tells the agent partial-name matching is allowed. The `course` parameter is never explained — no id-vs-name format, no relationship to `assignment` — leaving half the surface undocumented.

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?

The description states a specific verb-and-resource pair ("The full details of one Canvas assignment") and enumerates exactly what that entails: instructions, rubric, due date in the user's timezone, points, submission method, and submission status. That is enough to distinguish it from list-style siblings such as whats_due, but the description never names or contrasts a sibling to make the boundary explicit.

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: an agent can infer this is the tool for deep-diving a single assignment. There is no explicit when-to-use statement, no guidance on when a list-style sibling would be preferable, and no note on what happens if the name matches multiple assignments. The closing "never submit anything for the user" is a constraint rather than routing guidance.

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