Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Grep All Courses

grep_all_courses
Read-onlyIdempotent

Search all active Canvas courses by keyword in one request to find where a term appears; use course-specific search when the course is known to reduce API calls.

Instructions

Search every active course by keyword in one call. Read-only but uses many API calls; prefer search_course_content when you know the course.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "grep_all_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return (one page of results). Smaller is faster.
queryYesSearch text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
  2. Changed2 schema fields changedv1.1.3
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • addedInput schema / properties / query / description
      Added value: +"Search text."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the description does not need to restate safety. It adds genuinely useful context the annotations cannot convey: this fan-out across all courses is expensive in API calls. It does not say how large a page is by default or whether results are truncated before the limit applies.

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?

Two sentences with no filler. The capability is front-loaded and the cost/routing guidance follows immediately, so an agent can act after the first clause and refine after the second.

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 no-output-schema tool, the description never indicates what a match looks like (course metadata, matched content snippets, or both), which materially affects whether an agent needs a follow-up call. Cost and routing are covered, but the result shape and truncation behavior are not.

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% for both parameters, so query and limit are already documented, and the description only reinforces that the query is keyword-oriented. No extra syntax, matching behavior (substring vs token), or limit defaults are added. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (search), a specific scope (every active course), and the mechanism (keyword in one call). It also names the sibling tool it is not, so an agent can distinguish it from search_course_content without reading either schema.

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?

Explicitly gives the selection rule: use this for a global sweep, but prefer search_course_content when the course is already known. The alternative and the condition that selects it are both named, leaving nothing to inference.

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