Skip to main content
Glama

Read a learning path

get_learning_path
Read-only

Without a track: the learning paths (ordered reading lists through the blog). With one: its articles in reading order.

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
trackNoTrack id, e.g. "rust" or "llm". Omit to list them.
localeNoLanguage of the content: en or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the two behavioral modes and the ordering guarantee, but says nothing about pagination, defaults, or what a missing track yields; with annotations in place, that is adequate but thin.

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?

Two compact clauses, front-loaded with the mode distinction and free of filler. The telegraphic fragment style ('Without a track:') is efficient but slightly cryptic as an opening.

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 read-only, two-parameter tool with no output schema, the description covers both return shapes and the ordering behavior. Minor gaps remain around empty results and the locale parameter's effect on ordering/content, but nothing an agent needs to select and call it 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%, so both parameters are already documented, including the enum and the 'Omit to list them' note. The description restates the track behavior and adds the ordering semantics but no format or syntax detail beyond the schema; baseline 3 applies.

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 the two concrete payloads the tool returns (ordered reading lists, or a path's articles in reading order), which is specific enough to distinguish it from get_post and search. It does so elliptically, without an explicit verb identifying the tool as a reader, so it stops short of a 5.

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?

The 'Without a track / With one' framing gives real guidance on parameter-driven mode selection. However, it never states when to prefer this over siblings like search or get_post, nor any exclusions, so usage is only implied.

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.

Resources