Skip to main content
Glama

Axad

My lessons

list_lessons
Read-only

List the learner's lessons, the active ones first, then the closed ones, each with its language, page and progress. For a learner who wants to go on with something they studied.

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

Input Schema

NameRequiredDescriptionDefault
langNoOnly lessons in this language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the result ordering (active before closed) and the visible fields per lesson, which is genuine value. It is silent on result volume, pagination, and what "active vs closed" means operationally.

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 short sentences with no filler, and the ordering/content information is front-loaded before the usage hint. Every clause carries information.

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?

One optional parameter, no output schema, and annotations already handle safety, so the description's job is mostly to explain ordering and returned fields, which it does. The only real omission is any mention of the lang filter or result size limits.

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% and the single optional lang parameter is fully documented in the schema. The description never mentions the language filter, so it adds no meaning 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?

Specific verb plus resource ("List the learner's lessons") with the ordering rule (active first, then closed) and the per-item fields returned (language, page, progress). An agent knows exactly what it gets. It doesn't explicitly name a sibling to distinguish from, which keeps it from 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 trailing clause "For a learner who wants to go on with something they studied" implies a resume-learning scenario, which is real guidance. However, it offers no explicit exclusions or named alternatives such as browse_catalog or open_lesson, so the agent must infer when this is the wrong choice.

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.