Skip to main content
Glama

canvas_get_dashboard

Retrieve user dashboard details from the Canvas Learning Management System to manage courses, assignments, enrollments, and grades efficiently using the MCP server.

Instructions

Get user's dashboard information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler implementation that executes the canvas_get_dashboard tool by calling CanvasClient.getDashboard() and formatting the response as JSON text.
    // Dashboard
    case "canvas_get_dashboard": {
      const dashboard = await this.client.getDashboard();
      return {
        content: [{ type: "text", text: JSON.stringify(dashboard, null, 2) }]
      };
  • Tool schema definition including name, description, and empty input schema (no parameters required). Part of the TOOLS array used for registration.
    {
      name: "canvas_get_dashboard",
      description: "Get user's dashboard information",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • CanvasClient helper method that makes the API call to /users/self/dashboard and returns the dashboard data.
    async getDashboard(): Promise<CanvasDashboard> {
      const response = await this.client.get('/users/self/dashboard');
      return response.data;
    }
  • TypeScript interface defining the structure of the Canvas dashboard response (CanvasDashboard).
    export interface CanvasDashboard {
      dashboard_cards: CanvasDashboardCard[];
      planner_items: CanvasPlannerItem[];
    }
  • src/index.ts:1071-1073 (registration)
    Registration of the list tools handler that returns the full TOOLS array including canvas_get_dashboard.
    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 'Get user's dashboard information', implying a read-only operation, but doesn't specify authentication needs, rate limits, error handling, or what the return format looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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: 'Get user's dashboard information'. It's front-loaded with the core action and resource, with no unnecessary words or redundancy. This is appropriately sized for a simple tool with no parameters.

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?

Given the complexity of a dashboard tool (which could return varied data) and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'dashboard information' includes, how it's structured, or any behavioral aspects like permissions or errors. For a tool that likely aggregates data from multiple sources, more context is needed to guide effective use.

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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add any parameter information, which is acceptable here since there are no parameters to explain. A baseline score of 4 is appropriate as the schema fully covers the parameter semantics by indicating none are required.

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

Purpose3/5

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

The description 'Get user's dashboard information' clearly states the verb ('Get') and resource ('user's dashboard information'), making the purpose understandable. However, it's somewhat vague about what specific dashboard information is retrieved (e.g., cards, notifications, assignments) and doesn't distinguish it from sibling tools like 'canvas_get_dashboard_cards' or 'canvas_get_upcoming_assignments', which might overlap in scope.

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. It doesn't mention any prerequisites, context, or exclusions, and with siblings like 'canvas_get_dashboard_cards' and 'canvas_get_upcoming_assignments', there's no indication of how this tool differs or when it should be preferred over those.

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