Skip to main content
Glama

List the words of one lesson

scenario_learnables
Read-onlyIdempotent

Lists the words in a Memrise lesson with your learning state for each word, so you can see which vocabulary needs review. Returns partial results with warnings if some lesson links fail.

Instructions

List the words of one Memrise lesson (scenario) with the learner's state for each word. Fails if this lesson's details cannot be fetched. 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

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": {
      "scenario_id": "<scenario_id>"
    },
    "name": "scenario_learnables"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenario_idYesA lesson id from scenarios_list.
include_audioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare a safe, read-only, idempotent operation, but the description adds valuable behavioral context: failure when lesson details cannot be fetched, partial results with a warnings field, and notably slower first calls due to cold-cache fetching. This goes meaningfully beyond the annotations, though it does not fully describe the return shape.

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?

The description is compact and front-loads the core action and failure behavior. The cold-cache performance note is useful and short; the only slight inefficiency is that failure behavior is split across two sentences in a way that could be tightened.

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 two-parameter read-only list tool with no output schema, the description covers purpose, failure modes, partial results, and cold-cache performance. It is nearly complete, but it omits meaningful explanation of include_audio and does not describe the learner-state field shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides a description for scenario_id but not for include_audio, leaving schema coverage at 50%. The description says the tool lists one lesson's words but does not explain either parameter's effect, especially the include_audio option, so it does not compensate for the undocumented parameter.

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 a specific verb and resource: listing the words of one Memrise lesson with each word's learner state. It also clarifies that a scenario is a lesson, which helps an agent understand the domain object, though it does not explicitly contrast with siblings such as learnables_list or learnables_lookup.

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 implies this tool is for inspecting one specific lesson by id, and the schema points to scenarios_list for the id. It does not explicitly state when to use it instead of learnables_list or learnables_lookup, nor does it provide clear exclusion guidance.

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