Skip to main content
Glama
Sign In
steam-mcp

steam-mcp

by Praeses0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_config

Manage Steam game configuration by retrieving or setting launch options, applying presets, configuring MangoHud, and adjusting Steam settings.

Instructions

Launch options, presets, MangoHud, Steam settings

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": {
      "action": "<action>"
    },
    "name": "game_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
appidNo
actionYes
presetNo
optionsNo
settingsNo
mangohud_actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. The fragment only lists config domains and never states whether operations are reads or writes, whether settings persist, or what side effects occur. An agent cannot anticipate the behavior of actions like set_launch_opts or mangohud.

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

Conciseness2/5

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

Eight words make it concise, but conciseness crosses into under-specification: no sentence structure, no front-loaded purpose, and no information that helps invocation. It resembles labels rather than a structured tool description.

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

Completeness1/5

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

With six parameters, a required action enum, and no output schema or annotations, the description is far too thin. It omits behavior, return values, and any conditions, so an agent cannot reliably construct a call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needed to explain the six parameters, but it only restates the broad action domains. It does not clarify required fields (action), how preset/options/settings interact, or the meaning of mangohud_action beyond its enum name. Minimal thematic mapping, no semantic depth.

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

Purpose3/5

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

The description names a resource (game_config) and enumerates its domains: launch options, presets, MangoHud, Steam settings. However, it lacks a verb or explicit statement of what the tool does, and it doesn't differentiate it from sibling tools like game_control or diagnostics. This is enough for a vague orientation, not a clear purpose.

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?

There is no guidance on when to use this tool over siblings such as game_control, games, or diagnostics. No context, prerequisites, or exclusions are provided.

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

Deploy Server

Other Tools