Skip to main content
Glama

Printablesmith

Word scramble

make_word_scramble
Read-onlyIdempotent

Make a printable word scramble (unscramble the letters) or missing-letters sheet from a list of words, with an answer key. Good for spelling lists, vocabulary and party games.

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": {
      "words": "<words>"
    },
    "name": "make_word_scramble"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoscrambled: the letters mixed up; missing_letters: some letters blanked out.
seedNoWhich random version to make. Leave out for a fresh one; pass the seed from an earlier result to keep that version while changing other settings.
largeNoBigger, bolder letters for young children and beginning readers (for older eyes, use large_print).
paperNoPaper size: letter (US Letter, the default; US and Canada) or a4 (everywhere else).
titleNoThe title printed at the top of the sheet, e.g. "Winter Word Scramble". Keep it short.
wordsYesThe words, one per entry (2 to 40). Use plain, familiar words suited to the reader, e.g. "snowman", "mitten", "sled".
word_bankNoPrint the answers in a word bank.
decorationNoA themed border with matching pictures, drawn around the sheet: "line" for a plain border, "none" for nothing, or a theme such as halloween, christmas, thanksgiving, spring, dinosaurs, space, ocean, animals, birthday, back-to-school (95 themes; find_printables shows a theme’s name). Leave out for no border.
difficultyNoHow hard: easy, medium or hard.
large_printNoLarge print for older eyes or low vision: bigger, bolder letters and roomier layouts (sizes are capped to fit). For young children, use large.
letter_caseNoupper or lower case letters.
dyslexia_fontNoPrint in OpenDyslexic, a typeface some readers with dyslexia find easier.

Output Schema

NameRequiredDescriptionDefault
urlYesThe sheet on printablesmith.com, every setting filled in: open it to adjust, download the PDF or print
seedNoThe seed that rebuilds this exact sheet
makerYesWhich maker drew it, e.g. wordSearch
notesYesThings worth knowing about this sheet
titleYesThe sheet title
playUrlNoWhere a child can solve it on a screen (word search, crossword, maze, sudoku)
summaryYesWhat the sheet is
settingsYesThe address settings, as the maker reads them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the sheet is printable and ships with an answer key, but says nothing about repeatability, output volume, or how the word list is validated — gaps that matter little given the annotations but are still unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence states the product, the two modes and the answer key, followed by a short audience note. Purpose is front-loaded and no clause is redundant.

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 an output schema present and full parameter documentation, the description needn't explain return values, and it correctly covers the core intent. The main omission is differentiation from the many sibling maker tools, which would help an agent pick this one 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 description coverage is 100% and every parameter carries its own enum or prose explanation, so the baseline is 3. The description only summarizes the source input ("from a list of words") and the answer key, adding no meaning about mode, difficulty, word_bank, or decoration beyond what the schema already states.

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 names a specific verb and resource ("Make a printable word scramble") and enumerates both output modes ("unscramble the letters" and "missing-letters sheet") plus the answer key. It never names a sibling such as make_spelling_worksheet or make_cryptogram, so the agent must infer the boundary between this and adjacent word-puzzle tools.

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?

"Good for spelling lists, vocabulary and party games" gives a use context, which is more than nothing, but there is no when-to-use/when-not guidance and no routing toward alternatives. The agent is left to guess how this differs from the other word- and worksheet-making siblings.

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.

Resources