Skip to main content
Glama

Learn AI with Yaakov Tzedek

List AI courses

list_courses
Read-onlyIdempotent

The AI course catalogue on tzedek.me: video courses and short interactive courses, with a one line promise, lesson language, price as shown on the site and the course url. Filter with topic: one of agents, claude, chatgpt, build, video, google, work, models, or any free text (e.g. "n8n"). Use get_course for the syllabus.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly video courses or only interactive courses.
langNoContent language: "en" English (default) or "he" Hebrew.en
limitNo
topicNoTopic id (agents, claude, chatgpt, build, video, google, work, models) or free text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds the useful disclosure that prices are 'as shown on the site' and that each record includes a one-line promise, language and URL. It says nothing about what `limit` does when results are truncated (default 30, max 100) or whether a total count is returned, which matters for a list tool without an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly three dense sentences with the payload content front-loaded and the filter rule and sibling pointer following. The comma-list of returned fields is slightly run-on but every clause carries information.

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

Completeness4/5

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

With no output schema, the description does the necessary work of describing what each returned course record contains, and it covers the main filter. The remaining gap is pagination/limit behavior for a tool that defaults to 30 results.

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 coverage is 75% and the enums for `kind` and `lang` are already documented in the schema. The description adds only the free-text interpretation of `topic` with an example ("n8n"), while `limit` and `lang` semantics come entirely from the schema.

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?

The description names a specific verb and resource (listing the AI course catalogue on tzedek.me) and even enumerates the fields each entry carries. It separates itself from get_course by scoping that sibling to the syllabus, though it says nothing about how it differs from search_guides or get_learning_path.

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 gives a concrete usage rule for filtering (use `topic`, with the accepted ids and free-text allowed, e.g. "n8n") and explicitly routes syllabus-seeking callers to get_course. It does not state any when-not conditions or when another sibling list is preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.