Skip to main content
Glama

Wisely Arcade Games

recommend_games

Recommend up to 5 Wisely Arcade games for a player of a given age, optionally focused on one skill. Recommendations start from the gentlest 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": {
      "age": "<age>"
    },
    "name": "recommend_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesThe player's age in years.
skillNoOptional skill to focus on.

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?

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior beyond structured fields: a cap of 5 results and that recommendations are ordered from gentlest upward. It says nothing about whether age is bounded/clamped, what an unknown or out-of-range age yields, or what the result set looks like when no game matches a skill.

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?

A single front-loaded sentence with zero waste; the result cap, resource, and both scoping constraints are packed in without redundancy.

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 2-parameter read tool with full schema coverage and no output schema, the definition covers purpose, cap, and ordering. Only the return shape (what a recommended game record contains) and age edge-case behavior are left implicit, which is a minor gap.

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%, with both parameters (age, skill enum) fully documented in the schema, so the schema does the heavy lifting. The description only restates that age is required and skill is optional, adding no format, range, or interpretation detail beyond the schema.

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?

States a specific verb and resource ("Recommend up to 5 Wisely Arcade games") plus the scoping constraints (player age, optional skill). This distinguishes it in spirit from list_games/search_games, though no sibling is named explicitly.

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?

Usage is only implied by the purpose: an agent can infer it is the tool for "give me game suggestions for a 7-year-old who likes maths." There is no explicit when-to-use vs. list_games/search_games guidance and no stated exclusions or prerequisites.

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.