Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_app_details

Read-only

Retrieve complete Steam store details for any game, including descriptions, pricing, and system requirements, to get full app information from an ID.

Instructions

Get comprehensive store details for a game — the best 'tell me about X' tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.18.0
    • removedInput schema / $defs / AppDetailsInput / properties / appid / title
      Removed value: -"Appid"
    • removedInput schema / $defs / AppDetailsInput / properties / country_code / title
      Removed value: -"Country Code"
    • removedInput schema / $defs / AppDetailsInput / properties / include_long_description / title
      Removed value: -"Include Long Description"
    • removedInput schema / $defs / AppDetailsInput / properties / include_requirements / title
      Removed value: -"Include Requirements"
    • removedInput schema / $defs / AppDetailsInput / properties / language / title
      Removed value: -"Language"
    • removedInput schema / $defs / AppDetailsInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / AppDetailsInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / AppDetailsInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / AppDetailsInput / title
      Removed value: -"AppDetailsInput"
    • 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_app_detailsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_app_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?

The readOnlyHint annotation already covers the safety profile, and the description adds a small amount of scope context ('comprehensive store details'). It does not disclose behavioral details such as output format, default field inclusion, or potential size of the response, but given the read-only annotation, the description is adequate.

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, well-crafted sentence that front-loads the action and adds a value proposition. Every word earns its place and there is no unnecessary detail or repetition.

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 description gives a clear purpose but is vague about what 'comprehensive store details' actually includes, and without an output schema the agent cannot infer the response shape. The schema's parameters (response_format, include_long_description, etc.) partially fill this gap, but the description leaves key expectations implicit.

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?

The description does not mention any parameters or their semantics. Schema description coverage is 0% because the single top-level `params` property has no description, so the description would need to compensate but does not. The nested $defs do provide detailed parameter documentation, but the description itself adds no value beyond the schema.

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 uses a specific verb and resource ('Get comprehensive store details for a game') and positions itself as 'the best tell me about X tool,' which clearly distinguishes it from more specialized siblings like steam_get_app_reviews or steam_get_app_tags. An agent can immediately understand what this tool is for and where it fits among the alternatives.

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 a general use case ('tell me about X') but does not explicitly state when to use this tool over alternatives, nor does it name any sibling tools or exclusions. It gives a hint of context but leaves the routing decision to the agent.

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