Skip to main content
Glama

AI School by Lilly Tech Systems

by com.lillytechsystems

Search lessons

search_lessons
Read-onlyIdempotent

Search the AI School curriculum (500+ tracks, thousands of free lessons on AI engineering, governance, security, and applied AI by profession). Returns matching lesson titles and URLs. Use this before answering an AI-topic question when a concrete, citable lesson would help, then read_lesson to get the text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50)
queryYesWords to search for, e.g. "prompt injection defence"

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds the useful behavioral detail that results are lesson titles and URLs, and scopes the search across the given curriculum topics. It does not cover ranking or pagination, but those are minor for this kind of search tool.

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 three sentences with no filler: scope/curriculum, return value, and usage guidance with the read_lesson follow-up. It is front-loaded with the core action and remains highly readable.

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 simple search tool with complete parameter documentation, safety annotations, and a clear follow-up sibling, the description covers purpose, usage context, return shape, and workflow. Nothing essential for an agent 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%: 'query' and 'limit' are both documented in the input schema. The description does not add meaning beyond the schema, so the baseline of 3 applies.

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 names a specific verb ('Search'), a specific resource ('AI School curriculum'), and the concrete output ('matching lesson titles and URLs'). It also distinguishes itself from siblings by framing read_lesson as the follow-up step rather than the search 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?

It explicitly states when to use the tool: 'Use this before answering an AI-topic question when a concrete, citable lesson would help.' It also names the next step (read_lesson), though it does not explicitly describe when to prefer list_tracks or get_track instead.

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

All AI School by Lilly Tech Systems toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a clearly distinct entity and action: tracks are discovered and inspected via list_tracks/get_track, while lessons are searched and read via search_lessons/read_lesson. The descriptions explicitly guide when to use each tool, so there is no meaningful overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with appropriate singular/plural usage: get_track, list_tracks, read_lesson, search_lessons. The naming style is uniform, predictable, and immediately conveys each tool's purpose.

Tool Count5/5

Four tools is a well-scoped count for a read-only course content server: two for tracks and two for lessons. Each tool earns its place, and adding more would risk redundancy while removing any would create a discovery or reading gap.

Completeness5/5

The tool surface covers the full user journey for this domain: find a track, inspect its lesson list, search lessons across the curriculum, and read a lesson's full text. For a read-only educational content server, there are no obvious dead ends or missing operations.

Resources