Skip to main content
Glama

Get a published learning path

get_learning_path
Read-only

Use this tool for the published School sequence of one learning language in class-1, class-2, or class-3. Class 1 returns lessons only for a language with a published lesson track, in curriculum order. Class 2 and Class 3 return published exercises and share the class-page URL. If Class 1 is empty, the reason is no-published-class-1-track. No lesson is invented.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, from 1 to 20.
localeNoInterface locale code from the 77-locale registry, such as en, ru, ar, or zh-Hans.
offsetNoNumber of matches to skip.
classIdYes
learningLanguageYesInterface locale code from the 77-locale registry, such as en, ru, ar, or zh-Hans.

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 cover the read-only, closed-world, non-destructive safety profile, and the description adds real return-value behavior beyond them: class-1 yields lessons in curriculum order, class-2/3 yield exercises sharing the class-page URL, and an empty class-1 has reason no-published-class-1-track. It does not discuss pagination behavior or defaults for limit/offset, and there is no output schema to fill that gap.

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?

Four short sentences, front-loaded with the core scope and then the per-class behavior. 'No lesson is invented' is slightly oblique phrasing but carries a real meaning (no synthesized content) at minimal cost.

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

Completeness3/5

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

For a read-only getter with five parameters and no output schema, the description covers the class-conditional return content and the empty-result case, but says nothing about paging semantics (limit 1-20, offset) or result shape beyond lessons/exercises. Adequate but with clear gaps for an agent assembling a full call.

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 80%, so the baseline is 3; the description earns an extra point by explaining what each classId value actually returns and that 'No lesson is invented', which the enum alone cannot convey. It does not clarify the learningLanguage parameter, whose schema text oddly mirrors the locale registry wording, leaving a potential ambiguity unresolved.

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 (the published School learning-path sequence) and scopes it to one learning language within class-1/2/3, which is enough to separate it from generic siblings like get_resource or search_resources. The verb phrasing ('Use this tool for...') is weaker than an explicit 'Returns...' statement, keeping it just 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 Guidelines4/5

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

It gives clear selecting conditions: use it per learning language and per class, with the class-1 vs class-2/3 distinction spelled out. It does not name an alternative tool or state when not to use this one, so there is no explicit exclusion guidance.

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