Skip to main content
Glama

canvas_get_dashboard_cards

Retrieve dashboard course cards from Canvas LMS using the MCP server to access and manage course-related data efficiently.

Instructions

Get dashboard course cards

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in CanvasClient that executes the Canvas API call to retrieve dashboard cards from '/dashboard/dashboard_cards' endpoint.
    async getDashboardCards(): Promise<any[]> {
      const response = await this.client.get('/dashboard/dashboard_cards');
      return response.data;
    }
  • MCP tool handler in the CallToolRequestSchema switch statement that invokes the client method and formats the response.
    case "canvas_get_dashboard_cards": {
      const cards = await this.client.getDashboardCards();
      return {
        content: [{ type: "text", text: JSON.stringify(cards, null, 2) }]
      };
    }
  • src/index.ts:378-386 (registration)
    Tool registration in the TOOLS array used by ListToolsRequestSchema, including name, description, and empty input schema.
    {
      name: "canvas_get_dashboard_cards",
      description: "Get dashboard course cards",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • TypeScript interface defining the structure of Canvas dashboard cards returned by the tool.
    export interface CanvasDashboardCard {
      id: number;
      shortName: string;
      originalName: string;
      courseCode: string;
      assetString: string;
      href: string;
      term?: CanvasTerm;
      subtitle: string;
      enrollmentType: string;
      observee?: string;
      image?: string;
      color: string;
      position?: number;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Get') without details on permissions, rate limits, data format, or whether it's read-only or has side effects, leaving significant gaps for a tool that likely interacts with user data.

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, efficient sentence with no wasted words, making it easy to parse. It's front-loaded with the core action, though it could benefit from more detail given the lack of other context.

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 Canvas API tool with no annotations, no output schema, and sibling tools, the description is inadequate. It lacks details on behavior, output, and differentiation, failing to provide enough context for effective agent 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 parameter documentation is needed. The description doesn't add param info, which is appropriate, but it also doesn't clarify if any implicit parameters (like user context) are involved, slightly limiting completeness.

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 clearly states the verb ('Get') and resource ('dashboard course cards'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'canvas_get_dashboard' or explain what distinguishes 'cards' from the broader dashboard, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives such as 'canvas_get_dashboard' or 'canvas_list_courses'. The description lacks context about prerequisites, timing, or specific use cases, offering minimal 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