Skip to main content
Glama

Videogames Get Game

videogames_get_game
Read-onlyIdempotent

Get full details for a free-to-play game by its FreeToGame ID. Returns title, description, genre, platform, publisher, developer, release date, screenshots, and minimum system requirements.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 452
    },
    "name": "videogames_get_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFreeToGame game ID (e.g. 452 for "Valorant")

Output Schema

NameRequiredDescriptionDefault
idYesGame ID
genreYesGame genre
titleYesGame title
game_urlYesURL to play the game
platformYesPlatform availability
developerYesGame developer name
publisherYesGame publisher name
thumbnailYesURL to game thumbnail image
descriptionYesFull game description
screenshotsYes
release_dateYesGame release date
minimum_system_requirementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety needs no restating. The one genuine addition is the 'free-to-play' scope restriction, which tells the agent the corpus is limited; however, the field enumeration largely duplicates the output schema, and no not-found/invalid-ID behavior is disclosed.

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?

Two tight sentences with the trigger condition front-loaded in sentence one and the payload in sentence two; no filler. The field list is slightly wasteful given an output schema already exists.

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?

A one-parameter read tool with a full output schema and rich annotations needs little more, and the description correctly covers scope and payload. Minor gaps remain around error behavior for unknown or non-free-to-play IDs.

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% and the single 'id' parameter already carries its own description with a concrete example (452 for Valorant). The description adds nothing beyond restating that the ID is a FreeToGame ID, 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?

States a specific verb and resource ('Get full details for a free-to-play game by its FreeToGame ID') and enumerates the returned fields, so its single-record retrieval role is distinguishable from list/filter siblings. It never names those siblings explicitly, so differentiation is inferred from 'by its ... ID' rather than stated.

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: the requirement for a FreeToGame ID signals 'use this when you already have an ID from a list/search'. There is no explicit when-to-use versus list_games/filter_games, and no exclusion such as what to do when you only have a game name.

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.