Skip to main content
Glama

Search Tools

search_tools
Read-onlyIdempotent

Search this server's 200+ Canvas LMS tools by keyword to find the right tool and see matching disabled tools with instructions to enable them.

Instructions

Search this server's tools by keyword and return matching names with one-line descriptions. Read-only, makes no Canvas calls and works before a token is set. Use it to find the right tool among the 200+ available. A search also lists matching tools the tool profile or other settings switched off, and how to turn them on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoOptional group: identity, courses, assignments, submissions, grades, quizzes, discussions, inbox, calendar, content, groups, rubrics, search, planner, planning or meta.
queryNoKeyword to look for in tool names and descriptions, e.g. "grade". Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / group / description
      Previous value: -"Optional group: identity, courses, assignments, submissions, grades, quizzes, discussions, inbox, calendar, content, groups, rubrics, search, planning or meta."New value: +"Optional group: identity, courses, assignments, submissions, grades, quizzes, discussions, inbox, calendar, content, groups, rubrics, search, planner, planning or meta."
  2. Changed2 schema fields changedv1.0.2
    • addedInput schema / properties / group / description
      Added value: +"Optional group: identity, courses, assignments, submissions, grades, quizzes, discussions, inbox, calendar, content, groups, rubrics, search, planning or meta."
    • addedInput schema / properties / query / description
      Added value: +"Keyword to look for in tool names and descriptions, e.g. \"grade\". Omit to list everything."
  3. First observedv1.0.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds genuinely non-obvious behavior: it makes no Canvas calls, works before a token is set, and reports switched-off tools along with how to enable them. Those are exactly the details an agent can't infer from the structured fields.

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?

Three tight sentences, front-loaded with purpose, followed by the operational caveat and the discovery use case. No filler and no repetition of the title.

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?

For a two-optional-param, read-only search tool with no output schema, the description covers what it returns (names plus one-line descriptions), how it behaves without auth, and the unusual disabled-tools result. Nothing an agent needs to invoke it correctly is missing.

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%, so both query and group are already fully documented including the enumerated group values, and the description adds no syntax or formatting detail beyond 'by keyword'. Baseline 3 applies since 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 and resource ('Search this server's tools by keyword') plus the return shape ('matching names with one-line descriptions'). That clearly separates it from siblings like smart_search or search_course_content, which search content rather than the tool catalog itself.

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

Usage Guidelines4/5

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

Explicitly tells the agent when to reach for it: 'Use it to find the right tool among the 200+ available,' and adds the useful edge case that search also surfaces tools disabled by profile or settings. It doesn't name a competing discovery tool or state when-not to use it, so it stops short of a 5.

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