Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Puzzle themes

puzzle_themes
Read-onlyIdempotent

The built-in word search and crossword themes of the puzzle API. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": "puzzle_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond those structured fields - no indication of whether the result is a flat list of strings, page size, or caching behavior - and devotes its second sentence to unrelated API promotion.

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

Conciseness3/5

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

The first sentence is compact and front-loaded, but the second sentence is a marketing link with UTM tracking that gives no help in selecting or invoking the tool and dilutes the definition.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool with no output schema, the description should say what comes back - theme names, objects with categories, or grouped word-search vs crossword sets. That gap, plus the absence of any usage context, leaves the definition minimally adequate rather than complete.

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?

The tool takes zero parameters and the schema is closed (additionalProperties: false), so there is no parameter meaning for the description to convey. Baseline 4 applies for a genuinely parameterless tool.

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 identifies the specific resource: the built-in word search and crossword themes exposed by the puzzle API. It stops short of a verb (list/retrieve) and never states that it takes no inputs and returns the full set, but an agent can still tell what the tool surfaces.

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?

Naming the resource implies this is the tool to call when a puzzle theme value is needed, but there is no explicit when-to-use statement, no prerequisite, and no mention of how a caller should use the returned themes. Usage is left to inference.

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