Skip to main content
Glama

Details of one game

get_game
Read-onlyIdempotent

One game in detail: its editions and server types (vanilla, plugins, mods, modpacks), how many players each plan suits, how players join, whether it sleeps when empty, crossplay, mod sources, publisher terms and its settings. No account needed.

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

Input Schema

NameRequiredDescriptionDefault
gameYesA game name or id from find_games, such as "minecraft" or "terraria".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add context, which it does with "No account needed" (an auth requirement the annotations do not cover) and by inventorying the data returned. It does not describe behavior when the game is unknown, but the safety profile is fully covered.

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

Conciseness4/5

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

The core claim is front-loaded in the first words, and the long content enumeration is dense but each item tells the agent what information is available from the response. The closing "No account needed" is a short, useful trailing note rather than filler.

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 no output schema, the description must convey what comes back, and the enumeration of plan/server/settings aspects does that well for a single-resource lookup. Minor gaps remain: how a missing or ambiguous game name is handled and the exact shape of the returned settings.

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 the single parameter is documented with length bounds, an example ("minecraft", "terraria"), and its source (find_games). The prose adds no further meaning about the parameter, so the baseline of 3 applies.

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?

"One game in detail" states a specific verb-plus-resource, and the enumeration (editions, server types, player counts, join method, sleep behavior, crossplay, mod sources, publisher terms, settings) makes the scope concrete. It does not explicitly name a sibling such as find_games, so differentiation relies on the parameter description rather than the main text.

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 implied rather than stated: the schema for the game parameter says the name or id comes "from find_games", which tells the agent to look up the identifier first. There is no explicit when-to-use / when-not statement, and no guidance on when to use get_prices or list_regions alongside this tool.

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