Skip to main content
Glama

List lessons

list_lessons
Read-onlyIdempotent

List a learner's past lessons, newest first, with each lesson's space and kind (study or homework), so an agent can review prior answers, confidence and progress before tutoring.

Instructions

List the learner's lessons, newest first, each with its space and kind (study or homework; older ones teach or practice). total says how many match.

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
limitNoMost lessons to return (default 20).
space_idNoOnly the lessons of this space (from list_spaces), or "none" for lessons without a space. Leave it out for all lessons.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restatement. The description adds real context beyond them: results are sorted newest first, each row carries its space and kind, kind values are study/homework with older entries being teach/practice, and a 'total' count of matches is returned despite there being no output schema.

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?

A single sentence with no filler, and the most important facts (what is listed, sort order, return shape) come first. The parenthetical about kinds is compressed to the point of slight ambiguity, but it does not waste words.

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?

With no output schema, the description carries the burden of describing returns, and it does so reasonably: per-item space and kind plus a match total. For a two-parameter read-only list tool this is nearly complete, with only minor gaps such as whether results are paginated beyond limit.

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 (limit, space_id) are already fully documented in the schema, including the 'none' sentinel and default of 20. The description adds only the loose notion that lessons are associated with spaces, so 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 gives a specific verb and resource ('List the learner's lessons') plus ordering ('newest first') and the returned shape ('each with its space and kind'). It implicitly separates itself from read_lesson (single item) and list_spaces (spaces rather than lessons), though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the enumeration tool for lessons, and the schema's reference to 'from list_spaces' hints at a workflow. There is no explicit when-to-use, when-not-to-use, or named alternative for filtered or single-item retrieval.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.