Skip to main content
Glama

Wisely Arcade Games

list_games

List Wisely Arcade games, optionally filtered by age band (kids = ages 5-9, teens = 10-17, adults = 18+) and/or skill slug (memory, logic, maths, words, racing, strategy, knowledge).

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

Input Schema

NameRequiredDescriptionDefault
skillNoOptional skill filter.
age_bandNoOptional age band filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; "List" adequately suggests a read-style retrieval, and the filtering scope is clear. It does not disclose pagination, ordering, result limits, empty-result behavior, or access requirements, though those omissions are less severe for this simple listing operation.

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?

The single sentence is front-loaded with the operation and resource, followed by compact, functional filter details. The parenthetical enumerations earn their place, and there is no filler or repetition beyond the useful skill list.

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?

For a flat tool with two optional enum parameters, the description and schema provide enough information to invoke it correctly. Explicit sibling-selection guidance and basic collection behavior such as pagination or ordering would make it more complete, particularly because neither annotations nor an output schema are supplied.

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?

Although schema description coverage is 100%, the description adds useful meaning by mapping kids, teens, and adults to concrete age ranges and indicating through "and/or" that the filters may be combined. The skill-slug list largely repeats the schema enum, but the age definitions and combination semantics add genuine value.

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 uses a specific verb and resource, "List Wisely Arcade games," and clearly defines the available age-band and skill filters. It does not explicitly distinguish this broad listing operation from siblings such as search_games or recommend_games.

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?

The optional filtering implies that the tool is suitable for retrieving either a broad catalog or a subset by age and skill. However, there is no explicit when-to-use or when-not-to-use guidance, nor any direction for choosing between this tool and its 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.