Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Remote Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Smart Search

smart_search
Read-onlyIdempotent

Search a Canvas course by meaning using AI semantic search, with automatic fallback to keyword scanning when the beta endpoint returns 404.

Instructions

Search a course by meaning using Canvas's AI search. Read-only. It is a beta Canvas feature that often returns 404; when it does, this tool falls back to a keyword scan. search_course_content is the reliable keyword option.

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text.
filterNoOptional content types to search. Omit to search all four.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.3
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • addedInput schema / properties / filter / description
      Added value: +"Optional content types to search. Omit to search all four."
    • addedInput schema / properties / query / description
      Added value: +"Search text."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description provides crucial operational context beyond annotations by mentioning that it is a 'beta Canvas feature' and 'often returns 404.' While it doesn't detail retry logic or specific API constraints, detailing the failure mode significantly helps the agent manage expectations.

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 extremely concise and well-structured. It is front-loaded with the core functionality (AI search) and efficiently concludes with necessary limitations and directional advice regarding alternatives.

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

Completeness5/5

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

The combination of annotations (read-only status) and the description (AI nature, beta status, 404 fallback, keyword alternative) provides a complete picture of how an agent should approach this tool and handle its potential operational inconsistencies.

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?

With schema description coverage at 100%, the schema already provides comprehensive semantic detail for all parameters. Since the description focuses on the tool's operational behavior (AI, 404 status) rather than parameter definition, the score remains at the baseline 3.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Search a course by meaning using Canvas's AI search.' Furthermore, it distinguishes itself from the sibling tool 'search_course_content' by explicitly categorizing itself as the 'AI search' option.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides extremely clear usage guidelines by defining when to use this tool (search by meaning/AI) versus when to use the alternative ('search_course_content is the reliable keyword option'). This eliminates ambiguity for the calling agent.

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

Deploy Server

Other Tools