Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_package_details

Read-only

Retrieve store details for a Steam package using its package ID. Specify country code for regional pricing and choose markdown or JSON output.

Instructions

Get store details for a Steam package (a sub/bundle of one or more games).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.18.0
    • removedInput schema / $defs / PackageDetailsInput / properties / country_code / title
      Removed value: -"Country Code"
    • removedInput schema / $defs / PackageDetailsInput / properties / packageid / title
      Removed value: -"Packageid"
    • removedInput schema / $defs / PackageDetailsInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / PackageDetailsInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / PackageDetailsInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / PackageDetailsInput / title
      Removed value: -"PackageDetailsInput"
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"steam_get_package_detailsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_package_detailsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only safety is covered. The description adds scoping context that it operates specifically on packages, but it doesn't disclose rate limits, external API behavior, or output format beyond what annotations imply.

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?

A single, information-dense sentence that front-loads the core action and resource. No filler or repetition of the tool name.

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 read-only store-details lookup with well-documented parameters and a readOnlyHint annotation, the definition is nearly sufficient. It lacks an explicit statement of what fields 'store details' includes, but the response_format parameter and schema mitigate that gap.

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?

The description itself does not discuss parameters, but the input schema provides thorough descriptions for packageid (including the distinction from app IDs), country_code, and response_format. With rich schema coverage, the baseline of 3 applies despite no param info in the description.

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

Purpose4/5

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

The description states the specific action 'Get store details' and clarifies the resource as a Steam package (a sub/bundle of one or more games), which distinguishes it from app-level tools like steam_get_app_details. It doesn't explicitly name sibling alternatives, so it misses the top score.

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 package/bundle clarification implies this tool is for package IDs rather than app IDs, but no explicit when-to-use or alternative routing is given. The agent must infer when to select this over steam_get_app_details or steam_get_dlc.

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