Skip to main content
Glama
TMHSDigital

Steam MCP Server

by TMHSDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

steam_grantInventoryItem

Grant an inventory item to a player through the Steam partner API. Use for dev/test or server-side rewards; dry-run by default, requires confirm=true to send.

Instructions

MUTATES LIVE INVENTORY. Default dry_run=true; requires confirm=true to send. Grant an inventory item to a player via the partner API. Intended for dev/test or server-side rewards. Requires a publisher API key with server IP allowlisted in Steamworks partner settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appidYesSteam application ID
notifyNoWhether to notify the player of the grant (default: true)
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 to grant the item to
quantityNoNumber of items to grant (default: 1)
itemdefidYesItem definition ID from your Steamworks item schema

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.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and handles it well by flagging live mutation, the dry_run default, the confirm requirement, and the API key/IP allowlist prerequisite. It does not describe response shape or reversibility, but it covers the most critical behavioral hazards.

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 compact and front-loaded: the mutation warning appears first, followed by the safe-default and confirmation mechanics, then the purpose and prerequisites. Every sentence adds distinct value with no filler or repetition of schema details.

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 high-risk mutation tool with no annotations and no output schema, the description covers the essential operational context: it mutates live inventory, defaults to dry_run, requires confirm, names the intended use cases, and states auth prerequisites. It omits response/error detail, but the schema already describes the dry-run behavior and parameters.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented. The description adds meaningful semantics beyond the schema by explaining the dry_run/confirm interplay and emphasizing that confirm=true is required to actually send the request. This directly helps an agent use the two most safety-critical parameters correctly.

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 states a specific verb and resource: 'Grant an inventory item to a player via the partner API.' It also leads with 'MUTATES LIVE INVENTORY,' making the operation's nature unmistakable and distinguishing it from the many read-only Steam sibling tools.

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?

The description gives clear intended usage context: 'Intended for dev/test or server-side rewards' and specifies the prerequisite of a publisher API key with an allowlisted IP. It does not explicitly name alternatives or state when not to use the tool, but the context is sufficient for an agent to route appropriately.

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