Skip to main content
Glama

List word lists

list_word_lists
Read-only

Lists word lists as summaries (id, title, language, section, grade range, placement basis code, word count, page URL) without their words; returns { count, note, lists } in dataset order, all matches, no paging. Use this to discover ids, then get_word_list for one list's words; use get_words_for_grade or find_words instead when you want words directly. Filters combine with AND. A grade is a typical guide, not a rule: programs and standards differ, and it is not an assessment of any child. English lists are placed by grade; lists in other languages follow each language's own curriculum and have no grade.

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

Input Schema

NameRequiredDescriptionDefault
gradeNoKeep only English lists whose grade range includes this grade; other-language lists have no grade and are excluded. Omit for all grades.
sectionNocvc, families, sight, digraphs or patterns (English), or wordlist (every other-language list). Omit for all sections.
languageNoLanguage code: en, de, es, fr, nl or pt-br. Omit for all languages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / grade / description
      Previous value: -"English lists that cover this grade."New value: +"Keep only English lists whose grade range includes this grade; other-language lists have no grade and are excluded. Omit for all grades."
    • changedInput schema / properties / language / description
      Previous value: -"en, de, es, fr, nl or pt-br. Omit for all."New value: +"Language code: en, de, es, fr, nl or pt-br. Omit for all languages."
    • changedInput schema / properties / section / description
      Previous value: -"cvc, families, sight, digraphs, patterns or wordlist (other languages)."New value: +"cvc, families, sight, digraphs or patterns (English), or wordlist (every other-language list). Omit for all sections."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context beyond them: the return shape { count, note, lists }, dataset ordering, and explicitly 'all matches, no paging'. The caveat that a grade is a typical guide rather than a rule or assessment is useful framing, though it borders on advisory rather than behavioral detail.

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 what is returned and what is excluded ('without their words'), then routing, then filter semantics, then the grade caveat. Dense but ordered; the grade disclaimer is somewhat long and partially restates the schema's own grade description, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the return shape and paging/ordering behavior, and it fully covers the three optional enum filters plus how they combine. An agent has everything needed to call this correctly and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3; the description earns extra by stating that filters combine with AND and by clarifying that grade placement applies only to English lists while other languages follow their own curricula and have no grade. That adds cross-parameter meaning the schema's per-field descriptions do not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (lists word lists) and immediately scopes the output: summaries with enumerated fields, 'without their words'. It names the siblings it is not (get_word_list, get_words_for_grade, find_words), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: use this to discover ids, then get_word_list for one list's words; use get_words_for_grade or find_words when you want words directly. It also states how filters interact ('Filters combine with AND'), leaving nothing to inference about when this tool is the right 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.