Skip to main content
Glama
TMHSDigital

Steam MCP Server

by TMHSDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

steam_setAchievement

Unlock a specified achievement for a Steam player via the partner API. Use dry run first, then confirm with true to apply changes; designed for development and testing.

Instructions

MUTATES LIVE ACHIEVEMENT STATE. Default dry_run=true; requires confirm=true to send. Set (unlock) an achievement for a player via the partner API. Intended for dev/test use. Requires a publisher API key with server IP allowlisted in Steamworks partner settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appidYesSteam application ID
confirmNoRequired true when dry_run is false. Refuses otherwise.
dry_runNoIf true (default), return the planned request without contacting Steam
steamidYes64-bit Steam ID of the player
achievementYesAchievement API name (e.g. ACH_BEAT_LEVEL_1). Must match a name configured in Steamworks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Required true when dry_run is false. Refuses otherwise.",
+  "type": "boolean"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "If true (default), return the planned request without contacting Steam",
+  "type": "boolean"
+}
  2. First observedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and delivers: it flags destructive behavior ('MUTATES LIVE ACHIEVEMENT STATE'), discloses the safety default ('Default dry_run=true; requires confirm=true to send'), and documents auth prerequisites (publisher API key, allowlisted server IP). It stops short of describing idempotency or error behavior when the achievement is already set, but this is unusually transparent for an unannotated mutation tool.

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?

Four sentences, each earning its place: mutation alert, safety mechanism, operation definition, then context plus auth. The riskiest information is front-loaded ahead of the action statement, with zero filler across the whole text.

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?

For a 5-param mutation tool with no annotations and no output schema, the description covers the operational essentials: what it does, when to use it, how to avoid accidental mutation, and required credentials. The one real gap is return-value and error documentation for the confirmed send path, which neither the description nor an output schema addresses.

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%, so the schema already explains all five parameters in detail, including the dry_run/confirm interplay. The description's parameter-related content ('Default dry_run=true; requires confirm=true to send') merely restates the schema's own wording and adds no new semantics, warranting the baseline 3.

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 verb and resource: 'Set (unlock) an achievement for a player via the partner API.' The front-loaded 'MUTATES LIVE ACHIEVEMENT STATE' makes the operation type unmistakable, and the unlock framing distinguishes it from the sibling steam_clearAchievement.

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

Usage Guidelines4/5

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

Explicitly scopes usage to 'Intended for dev/test use,' giving clear context for when the tool is appropriate and implicitly steering away from production. It does not name sibling alternatives like steam_clearAchievement for the reverse operation, but the dev/test framing plus the dry_run/confirm guardrail conveys intent clearly.

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