Skip to main content
Glama

List learner words

learnables_list
Read-onlyIdempotent

List Memrise words for the configured language pair with lessons and topics. Filter by any or fully learned/known state and paginate truncated results with next_after_id.

Instructions

List the learner's Memrise words for the configured language pair, each with the lessons and topics that teach it. state: 'any' (default) = every word you have met; 'fully_learned_or_known' = only fully learned or already-known words. Returns total, returned and truncated (default limit 200). When truncated is true the result also has next_after_id: call again with after_id set to next_after_id; repeat until truncated is false. 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": "learnables_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoany
after_idNo
include_audioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Goes well past the annotations by disclosing return envelope fields (total, returned, truncated), the partial-failure contract where lesson links are dropped and a `warnings` field names failed lesson ids, and a latency characteristic (first call in a cold-cache process is slower). The annotations already cover safety/idempotency, and the description adds the operational traits an agent actually needs.

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?

Front-loaded with the purpose, then pagination, then degradation and performance in a logical order; every sentence carries information. It is dense to the point of being cramped — the state semantics and pagination rules are packed into long clauses — but no sentence is filler.

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 usefully enumerates the return envelope and the warnings field, and covers the pagination and cold-cache behaviors an agent must plan around. The one substantive hole is include_audio, and the absence of any routing cue versus learnables_lookup leaves a small selection gap.

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?

With 0% schema coverage the description carries the full burden, and it delivers: it defines both state enum values, ties limit's default of 200 to the truncation contract, and explains how to source and use after_id from next_after_id. The gap is include_audio, which is never mentioned, so an agent has no clue what it toggles; limit's 10000 maximum is also unstated.

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 concrete verb and resource — 'List the learner's Memrise words for the configured language pair' — plus the enrichment (lessons and topics). It is unambiguous about scope, but never mentions the closest sibling (learnables_lookup) or explains how this differs from a single-word lookup, leaving the agent to infer the distinction from the name alone.

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?

Gives real operational guidance for the pagination loop ('call again with after_id set to next_after_id; repeat until truncated is false') and explains when state='fully_learned_or_known' is the right choice. However, it offers no when-to-use/when-not guidance relative to alternatives such as learnables_lookup or scenario_learnables, so tool selection is only implied.

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