gamelibs-mcp

steam_list_games

List your owned Steam games with filters for installed status, name search, sorting, and pagination to retrieve detailed library information.

Instructions

List owned Steam games (thin: appid, name, playtime, last-played, installed).

Args: installed_only: Only games installed on THIS machine (requires local Steam). search: Case-insensitive substring match on the game name. sort: One of "playtime" (desc), "name" (asc), "last_played" (desc). limit: Page size (1-500). offset: Pagination offset.

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": "steam_list_games"
  }
}

Input Schema

Name	Required	Default
`sort`	No	playtime
`limit`	No
`offset`	No
`search`	No
`installed_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 31, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses the thin return shape, case-insensitive search behavior, sort semantics, and a local-Steam prerequisite. However, it omits other important traits such as authentication needs, data freshness/caching behavior, or pagination response behavior.

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 one-line purpose is front-loaded and instantly clear, followed by a compact Args block with no filler. Every sentence adds meaningful information about output or parameters.

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?

Given there is no output schema, the description appropriately names the returned fields and covers all parameters. It is nearly complete for correct invocation, though it could additionally mention whether Steam authentication is required and whether results are cached.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates by explaining every parameter: installed_only, search case-insensitivity, exact sort options with ordering, limit range, and offset meaning. This goes well beyond the bare schema properties and is essential for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action and resource: 'List owned Steam games'. It also defines the exact fields returned with 'thin: appid, name, playtime, last-played, installed', which distinguishes it from detail-oriented siblings like steam_get_game_details and platform-specific siblings like epic_list_games.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides parameter-level context such as 'installed_only requires local Steam', but never explains when to choose this tool over alternatives like steam_get_game_details or epic_list_games. There is no explicit when/when-not guidance for selecting this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server