Skip to main content
Glama

Learn AI with Yaakov Tzedek

Learning path for a goal

get_learning_path
Read-onlyIdempotent

An ordered learning path for a goal such as "build AI agents", "AI for marketing", "Claude Code", "automate my business" or "make AI videos": a quick interactive course first, then the most relevant free guides, then the in depth video course, all real items from the tzedek.me catalogue with their urls.

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": {
      "goal": "<goal>"
    },
    "name": "get_learning_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesWhat the learner wants to be able to do.
langNoContent language: "en" English (default) or "he" Hebrew.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add behaviour beyond that. It does so usefully: it discloses the ordered structure of the result, that items are real catalogue entries, and that URLs are included. What it omits is how well the goal must match to return anything meaningful, and that the result may be empty.

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?

The core claim is front-loaded (what the tool returns and its ordered composition). The list of example goals is long but each example genuinely constrains the expected input, so it earns its space; a slightly tighter phrasing of the three-stage sequence would make it a 5.

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 carries the burden of explaining the return shape and does so adequately by describing the ordered stages and included URLs. For a two-parameter read-only lookup this is close to sufficient; missing only edge-case behaviour (empty results, language handling) to be complete.

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 the schema already documents both the goal and the en/he language enum with its default, establishing a baseline of 3. The example goals add some intuition about granularity for 'goal', but the lang parameter and its effect on the returned path are never mentioned in the 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?

The description states a specific resource: an ordered learning path for a stated goal, with a defined three-stage composition (interactive course, free guides, in-depth video course) drawn from the tzedek.me catalogue. It is clearly distinct from single-item siblings like get_course and get_guide, though it never explicitly names the distinction.

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

Usage Guidelines3/5

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

Concrete example goals ("build AI agents", "Claude Code", "automate my business") implicitly signal the intended use case of asking for a curated multi-item roadmap. However, there is no explicit when-to-use versus when-to-use search_guides or get_course, and no guidance on fallback behaviour when the goal is not represented in the catalogue.

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.