Skip to main content
Glama

Words for a grade

get_words_for_grade
Read-only

Returns every different English word from all lists whose grade range includes a grade, deduplicated, each with the ids of the lists it comes from, plus totalDifferentWords and returned. Words come in dataset list order and are cut at limit (no offset or paging). Use this for a grade-wide pool; use get_word_list for one specific list, or find_words to search by letter pattern. 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

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": {
      "grade": "<grade>"
    },
    "name": "get_words_for_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
gradeYesRequired grade: pre-k, kindergarten, grade-1, grade-2 or grade-3.
limitNoMaximum words to return, 1 to 1500. Default 300; compare returned with totalDifferentWords to see if the result was cut.
sectionNoOnly lists in this section, e.g. sight or cvc. wordlist (other languages) gives no words here. Omit for all sections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / grade / description
      Previous value: -"pre-k, kindergarten, grade-1, grade-2 or grade-3"New value: +"Required grade: pre-k, kindergarten, grade-1, grade-2 or grade-3."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum words to return. Default 300."New value: +"Maximum words to return, 1 to 1500. Default 300; compare returned with totalDifferentWords to see if the result was cut."
    • addedInput schema / properties / section / description
      Added value: +"Only lists in this section, e.g. sight or cvc. wordlist (other languages) gives no words here. Omit for all sections."
  2. First observed

TDQS

A4.2/5.0
Behavior3/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 still adds real behavior: dataset list ordering, truncation at limit with no offset or paging, the totalDifferentWords vs returned comparison for detecting cuts, and the caveat that grade placement is a guide rather than a rule. It stops short of describing error behavior or the shape of each word record's list ids, keeping it at a solid but not exceptional level.

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 contract, then routing, then the caveat; no filler sentences. The grade-is-a-guide paragraph is slightly long for its role but serves interpretation of results, so it still earns its place.

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 carries the return contract itself and does so: deduplicated words, source list ids, totalDifferentWords and returned, ordering, and truncation. For a read-only, three-parameter lookup this is sufficient to call and interpret 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%, so the baseline is 3; the schema already documents grade enum, limit range, and section enum. The description adds cross-parameter meaning — no offset or paging, and wordlist producing no words here — which is modest added value over an already complete schema.

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 deduplicated English words across all lists whose grade range includes the grade), names the exact return fields, and explicitly contrasts itself with get_word_list and find_words. An agent can distinguish it from every sibling without opening a 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 selection rule: use this for a grade-wide pool, get_word_list for one list, find_words for letter patterns. It also states when the section filter yields nothing (wordlist for other languages) and that non-English lists have no grade, so the agent knows the boundaries of valid use.

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.