Skip to main content
Glama

List lessons

scenarios_list
Read-onlyIdempotent

Lists a Memrise learner's completed or in-progress lessons, sorted newest completed first, with progress and start/completion dates so you can review study history and current activity.

Instructions

List the learner's Memrise lessons (scenarios) of one type, newest completed first, with progress and the start and completion dates. type: 'completed' (default) or 'in_progress'. If some lesson details cannot be fetched, results are still returned without those lesson links and a warnings field names the failed lesson ids. The first call in a fresh process with a cold cache is noticeably slower because every completed lesson is fetched once; later calls are fast.

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

Input Schema

NameRequiredDescriptionDefault
typeNocompleted
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses result ordering, graceful degradation on partial failures (results returned minus failed links, plus a `warnings` field naming failed lesson ids), and cold-cache performance characteristics. These are exactly the operational traits an agent needs and that annotations cannot express.

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 dense paragraph that front-loads what the tool returns and the ordering, then adds caveats. Every sentence carries information, though the cache-latency note could be split out for scannability.

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 does describe return content (progress, start and completion dates, `warnings`) and failure behavior, which covers most of the tool's complexity. The undocumented `since` parameter is the one meaningful gap for a two-parameter tool.

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 0%, so the description must carry parameter meaning. It fully explains `type` (values and default), but the `since` parameter is never mentioned at all, leaving its date/date-time semantics and filtering effect unexplained.

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?

States a specific verb and resource ('List the learner's Memrise lessons (scenarios)') and clarifies the naming overlap between lessons and scenarios. It also specifies ordering ('newest completed first') and returned fields, but never contrasts itself with siblings such as learnables_list or scenario_learnables.

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 description gives the 'type' values and default, which implies when each mode applies, and warns about first-call latency. It offers no explicit when-to-use or when-not-to-use guidance against the sibling listing tools, leaving the choice to inference.

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