Skip to main content
Glama

classroom_search_courses

Read-only

Search Google Classroom courses by name or section using a case-insensitive filter. Returns paginated results with a nextPageToken to continue until no matches remain.

Instructions

Search courses by name or section (client-side filter, case-insensitive). Returns one page as {items, nextPageToken}; continue until nextPageToken is null.

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": "classroom_search_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesString to search for in course name or section
fullDataNo
pageSizeNo
pageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • removedInput schema / properties / query / minLength
      Removed value: -1
  2. First observedv3.0.0-beta.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real context beyond them: filtering happens client-side, matching is case-insensitive, and results come back paginated as {items, nextPageToken}. It does not say how large the underlying course set is or whether all courses are fetched before filtering, which is the main remaining behavioral unknown.

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 dense sentences with zero filler; the search semantics come first and the return/pagination contract second. Every clause carries information an agent needs.

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?

Return shape and pagination are well covered despite no output schema, and the read-only nature is confirmed by annotations. However, with four parameters and only 25% schema coverage, the unexplained fullData flag is a genuine gap in a definition that is otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% β€” just 'query' is documented, and the description merely restates that it matches name or section. pageToken is indirectly explained via the nextPageToken continuation rule, but pageSize and especially the fullData boolean are left completely undefined in both schema and description.

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?

Specific verb plus resource plus scope: 'Search courses by name or section' tells the agent exactly what is matched. It implicitly contrasts with classroom_list_courses (search vs. list) but never names the sibling, so the differentiation is left to inference.

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?

The parenthetical 'client-side filter, case-insensitive' tells the agent this is not a server-side query, which materially changes expected behavior and cost. 'Continue until nextPageToken is null' is explicit pagination guidance, though no when-not-to-use or named alternative is given.

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