steam-local-mcp

Find installed Steam games

steam_find_game

Read-only

Search your local Steam library for installed games by name or numeric app ID to locate them quickly.

Instructions

Find locally installed Steam games by name or app ID.

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": {
      "query": "<query>"
    },
    "name": "steam_find_game"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Installed game name or numeric Steam app ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotation declares readOnlyHint=true, so no contradiction. The description does not add behavioral context beyond the basic function (e.g., partial matching, case sensitivity, behavior on not found). With annotations covering safety, a score of 3 is appropriate.

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 description is a single, efficient sentence with no wasted words. It front-loads the key action and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema. The description lacks details on return format (e.g., list of games or single result), error handling, or matching behavior. A more complete description would clarify output and edge cases.

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%. The tool description's parameter description ('Installed game name or numeric Steam app ID.') duplicates the schema description, adding no extra meaning. Baseline 3 is correct.

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?

The description clearly states the action ('Find'), the resource ('locally installed Steam games'), and the search criteria ('by name or app ID'). It effectively distinguishes the tool from siblings like steam_get_library (list all) and steam_search_store (online store).

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 description implies usage for searching by name or app ID but does not explicitly state when to use this tool over alternatives like steam_get_library or steam_get_game_install_status. No when-not or alternative guidance is provided.

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

Deploy Server