Skip to main content
Glama

canvas_get_upcoming_assignments

Retrieve upcoming assignment due dates from Canvas LMS. Specify a limit to control the number of assignments returned, helping users stay organized and manage deadlines effectively.

Instructions

Get upcoming assignment due dates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of assignments to return

Implementation Reference

  • Core handler function that implements the tool logic by calling Canvas API endpoint `/users/self/upcoming_events` and filtering for assignments.
    async getUpcomingAssignments(limit: number = 10): Promise<CanvasAssignment[]> {
      const response = await this.client.get('/users/self/upcoming_events', {
        params: { limit }
      });
      return response.data.filter((event: any) => event.assignment);
    }
  • MCP CallToolRequestSchema handler case that receives arguments, calls CanvasClient.getUpcomingAssignments, and returns formatted JSON response.
    case "canvas_get_upcoming_assignments": {
      const { limit = 10 } = args as { limit?: number };
      const assignments = await this.client.getUpcomingAssignments(limit);
      return {
        content: [{ type: "text", text: JSON.stringify(assignments, null, 2) }]
      };
    }
  • Tool schema definition with name, description, and inputSchema for 'limit' parameter. Part of TOOLS array.
    {
      name: "canvas_get_upcoming_assignments",
      description: "Get upcoming assignment due dates",
      inputSchema: {
        type: "object",
        properties: {
          limit: { type: "number", description: "Maximum number of assignments to return" }
        },
        required: []
      }
    },
  • src/index.ts:1071-1073 (registration)
    Registration of ListToolsRequestSchema handler that returns the full TOOLS array containing this tool.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS
    }));
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't specify authentication requirements, rate limits, pagination, or what 'upcoming' means (e.g., time frame, sorting). This leaves significant gaps in understanding how the tool behaves in practice.

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?

The description is a single, clear sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning the highest score for brevity and structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and one parameter, the description is incomplete. It lacks details on behavioral aspects like authentication, error handling, or the definition of 'upcoming,' and doesn't clarify the return format. This leaves the agent with insufficient context to use the tool effectively beyond basic invocation.

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 100%, with the 'limit' parameter fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as default values or how 'limit' interacts with 'upcoming.' Given the high coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 'Get upcoming assignment due dates' clearly states the verb ('Get') and resource ('upcoming assignment due dates'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'canvas_list_assignments' or 'canvas_get_assignment', which could also retrieve assignment information, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'canvas_list_assignments' that might list all assignments, there's no indication that this tool specifically focuses on 'upcoming' or 'due dates,' leaving the agent to infer usage context without explicit direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DMontgomery40/mcp-canvas-lms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server