Skip to main content
Glama

Dictionary of Applied Machine Learning

Read one reading order

get_learning_path
Read-onlyIdempotent

One reading order with the abstract of every term in it, in the order to read them. Give either topic or terms; giving neither returns the list of available reading orders.

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

Input Schema

NameRequiredDescriptionDefault
termsNoAn explicit reading order instead of a curated one: term keys or display names, kept in the given order. This is the form a selection on alexjung.at/baukasten/ takes, whose URL fragment reads '#terms=llm,transformer'.
topicNoWhich reading order to return: a path id (e.g. 'llm', 'grundlagen', 'mathematik') or words from its title or its audience note. Matching is case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / terms / description
      Added value: +"An explicit reading order instead of a curated one: term keys or display names, kept in the given order. This is the form a selection on alexjung.at/baukasten/ takes, whose URL fragment reads '#terms=llm,transformer'."
    • addedInput schema / properties / terms / minItems
      Added value: +1
    • addedInput schema / properties / topic / description
      Added value: +"Which reading order to return: a path id (e.g. 'llm', 'grundlagen', 'mathematik') or words from its title or its audience note. Matching is case-insensitive."
    • addedInput schema / properties / topic / minLength
      Added value: +1
  2. Added

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 closed-world behavior, so the safety profile is covered. The description adds real behavioral context: the return payload bundles every term's abstract in reading order, and omitting both parameters degrades to a listing rather than an error. Undisclosed behavior remains for unmatched `topic` values (no result vs. error).

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 sentences, front-loaded with the payload description and followed by the parameter-selection rule. No filler, no repetition of the title.

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?

For a two-optional-parameter read tool with full schema coverage, no output schema, and safe annotations, the description covers what is returned and how to parameterize it. The only gap is failure behavior for a `topic` that matches nothing, which the description does not state.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a constraint the schema does not enforce: the two parameters are mutually exclusive alternatives ('Give either `topic` or `terms`'), which prevents an agent from sending both. Format details (path ids, display names, URL fragment) are already carried by 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 resource and scope: one reading order plus the abstract of every term in it, ordered for reading. It implicitly contrasts with the list-oriented sibling by describing the fallback ('giving neither returns the list of available reading orders'), though it never names list_learning_paths directly.

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?

It explains the calling forms ('Give either `topic` or `terms`') and what happens when neither is supplied, which is useful invocation guidance. It does not say when to prefer this over get_related_terms, lookup_term, or list_learning_paths, so an agent must infer the boundary itself.

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.