Skip to main content
Glama

Wisely Arcade Games

get_game

Get full details for one Wisely Arcade game by its slug (for example "chess" or "letter-garden").

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": {
      "slug": "<slug>"
    },
    "name": "get_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe game slug, as used in its URL.

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?

No annotations are supplied, so the description must carry behavior alone. "Get" and "full details" signal a read-only, single-record fetch, which is good, but nothing is said about what happens on a bad slug (error vs. empty), whether the response includes nested data, or whether access is public.

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 sentence, front-loaded with the verb and resource, with the examples placed where they help most. Nothing redundant and nothing padded.

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 one-parameter lookup with no output schema, the description covers what is returned ("full details") and how to address a record. The only meaningful gap is the error path for a nonexistent slug, which is low-risk for a read tool.

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?

Schema coverage is already 100% ("The game slug, as used in its URL"), so the baseline is 3. The description adds concrete example values ("chess", "letter-garden"), which clarifies the actual slug format beyond what the schema 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?

"Get full details for one Wisely Arcade game by its slug" names a specific verb (get), a specific resource (one game), and the lookup key (slug). "One" implicitly contrasts with the list/search siblings, though no sibling is named explicitly, so it falls short of a 5.

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 phrase "by its slug" implies this tool is for when you already have an identifier, which implies list_games or search_games must run first to obtain one, but that workflow is never stated. There are no explicit when-not conditions or fallback guidance for an unknown slug.

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.