Skip to main content
Glama

Dictionary of Applied Machine Learning

List the reading orders

list_learning_paths
Read-onlyIdempotent

The author's curated reading orders through the dictionary: one per topic (how ChatGPT works, AI foundations, explainable and trustworthy AI, mathematics of AI, ...), each with its audience and its terms in the order to read them. Takes no arguments. Use when someone asks what to learn, read, or teach about a topic, or how to structure a course or seminar, so the answer follows the author's order instead of an improvised one.

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_learning_paths"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful substance beyond that: it returns every topic's path with audience and ordered terms, which tells the agent how much data to expect.

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?

Front-loaded with what is returned, then when to use it; there is little waste. The parenthetical topic list is slightly long but earns its place by making the content concrete.

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?

No output schema exists, and the description compensates by describing the return shape (per-topic paths with audience and ordered terms). For a trivial zero-argument list tool with full annotations, nothing material is missing.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. The description's 'Takes no arguments' is consistent with the empty schema and confirms no filtering option exists.

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?

States a specific verb and resource ('curated reading orders through the dictionary'), plus the granularity ('one per topic') with example topics. An agent can infer it differs from the singular get_learning_path, though the sibling is never named.

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?

Gives concrete triggering situations — asking what to learn, read or teach, or how to structure a course or seminar — and states the intent (follow the author's order, not an improvised one). It does not name get_learning_path as the alternative when a single topic's path is wanted.

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.