Skip to main content
Glama

Save Canvas deadlines to memory

sync_canvas
DestructiveIdempotent

Save upcoming Canvas deadlines into each class's folder in Thread memory, with an option to fetch fresh data from Canvas when assignments were just posted or changed.

Instructions

Save upcoming Canvas deadlines into each class's folder in Thread memory. refresh: true asks Canvas right now instead of using answers saved in the last few minutes (deadlines), day (class list) or week (syllabus); use it when the person says something was just posted or changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
refreshNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations flag destructiveHint=true, yet the description never says what is overwritten or whether previously saved deadlines are replaced on re-sync. It does add genuine value by disclosing the cache TTL layers (minutes for deadlines, day for class list, week for syllabus), which the annotations do not.

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?

Two sentences, front-loaded with the action, and no filler. The parenthetical cache explanation is dense but earns its place; minor awkwardness from the inline line breaks.

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 no explanation, but for a tool marked destructive the definition is silent on overwrite behavior, and the `days` window is unexplained. Adequate but with material gaps.

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%, and the description compensates well for `refresh` by explaining the staleness window it bypasses. However, `days` (default 14) is never mentioned, leaving half the parameters undocumented anywhere.

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 concrete verb and resource with destination: "Save upcoming Canvas deadlines into each class's folder in Thread memory." That is specific enough to separate it from listing tools like whats_due or canvas_assignment, though no sibling is named explicitly.

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?

Gives clear when-to-use guidance for the `refresh` flag (the person says something was just posted or changed), but offers no guidance on when to call this at all versus whats_due, canvas_assignment, or the calendar tools.

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