Skip to main content
Glama

get_todo_items

Retrieve todo items—assignments requiring action—for the authenticated Canvas user to identify pending work and prioritize tasks.

Instructions

Get todo items (assignments that need action) for the authenticated user

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": "get_todo_items"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: it is a read ('Get') scoped to the authenticated user, and it filters to actionable assignments rather than everything. It says nothing about sorting, cross-course aggregation, whether completed items are excluded, or response shape.

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?

A single sentence with the resource stated first and the qualifier immediately after; no filler or redundant phrasing.

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 zero-argument read tool this covers the essentials of what and for whom, but with no output schema and no description of what each item contains (course, due date, completion state), the agent cannot anticipate the response.

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

Parameters4/5

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

The tool takes zero parameters, so the schema baseline is 4. The phrase 'for the authenticated user' usefully explains why no user identifier is needed, which is the only semantic point worth making here.

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 ('Get todo items') and adds a parenthetical definition ('assignments that need action') plus a scope ('for the authenticated user'). This meaningfully separates it from a raw 'get_assignments' list, though it never names a sibling to contrast with 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?

Usage is only implied: 'items that need action' hints this is a pending-work view rather than a full assignment list. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., get_upcoming_assignments) to route the agent.

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