Skip to main content
Glama

Get one word list

get_word_list
Read-only

Returns one word list in full: the list summary plus every word, its groups (for example -at, -an, -ap families), placementBasisDetail (null for lists in other languages), license and citation text. Use this when you know the list id from list_word_lists; use get_words_for_grade for words merged across a grade's lists, or find_words to search by letter pattern. An unknown id returns an error that points to list_word_lists.

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": {
      "id": "<id>"
    },
    "name": "get_word_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact list id as returned by list_word_lists (case-sensitive), e.g. short-a, kindergarten, vowel-teams; other-language ids carry a language prefix, e.g. es:palabras-con-m.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"List id, e.g. short-a, kindergarten, vowel-teams, or es:palabras-con-m"New value: +"Exact list id as returned by list_word_lists (case-sensitive), e.g. short-a, kindergarten, vowel-teams; other-language ids carry a language prefix, e.g. es:palabras-con-m."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real context on top: the list is returned in full rather than paginated, placementBasisDetail is null for other-language lists, and an unknown id yields an error pointing to list_word_lists. It does not discuss payload size or performance for large lists, which is the only remaining behavioral gap.

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 return shape, then routing guidance, then error behavior — a sensible order with no filler. The single sentence listing returned fields is dense with enums and parentheticals, but every clause carries information.

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 takes on the burden and discharges it by naming the returned fields (summary, words, groups, placementBasisDetail, license/citation) and the failure mode. Combined with a single fully documented parameter, an agent has everything needed to call it correctly.

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 coverage is 100% and the id parameter already documents case-sensitivity, the list_word_lists provenance, and language-prefixed ids. The description only reinforces that the id is known from list_word_lists without adding new syntax or format detail, so the baseline 3 applies.

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 ("Returns one word list in full") and immediately enumerates what the payload contains: list summary, every word, groups, placementBasisDetail, license and citation text. This is clearly separable from siblings like get_words_for_grade (merged across lists) and find_words (pattern search).

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 trigger ("Use this when you know the list id from list_word_lists") and names two alternatives with the conditions that select them: get_words_for_grade for words merged across a grade's lists, find_words for letter-pattern search. It also documents the recovery path for a bad id.

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.