Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_search_apps

Read-only

Find a Steam game's appid by its exact or partial title. Use when you know the name but need the numeric ID for API calls or integrations.

Instructions

Look up a game's appid by its title — when you already know the name and need its ID (not for discovery, recommendations, or buy decisions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.18.0
    • removedInput schema / $defs / AppSearchInput / properties / country_code / title
      Removed value: -"Country Code"
    • removedInput schema / $defs / AppSearchInput / properties / language / title
      Removed value: -"Language"
    • removedInput schema / $defs / AppSearchInput / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / $defs / AppSearchInput / properties / query / title
      Removed value: -"Query"
    • removedInput schema / $defs / AppSearchInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / AppSearchInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / AppSearchInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / AppSearchInput / title
      Removed value: -"AppSearchInput"
    • 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_search_appsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_search_appsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation covers the safety profile, and the description is consistent with a read-only lookup. It adds the scoping nuance (only for known titles) but doesn't disclose additional behavioral details like result format, failure modes, or potential for partial matches. Since annotations already declare read-only, this is acceptable but not enriching.

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, front-loaded sentence with zero waste. The primary purpose and key exclusion are stated immediately, making it highly efficient for an agent to parse and act on.

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?

For a lookup tool with moderate complexity (5 parameters), the description is adequate but misses details on output format (list vs single appid), behavior on no match, and the meaning of response_format. Given no output schema and minimal description, an agent might be uncertain about the expected return. However, the tool is simple enough that a 3 is fair.

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 adds no parameter-specific meaning beyond mentioning 'title', which maps to the query field. The schema provides descriptions for query, limit, and language, but country_code and response_format have none, and the description doesn't help clarify them. With 0% parameter coverage from the description and incomplete schema coverage, this is a notable gap.

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 clearly states the verb (look up), resource (appid), and context (by title). It explicitly contrasts with discovery, recommendations, and buy decisions, which helps the agent distinguish it from siblings like steam_discover, steam_recommend, and steam_should_i_buy.

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?

It specifies when to use (when you already know the name) and when not to use (not for discovery, recommendations, or buy decisions). While it doesn't name specific alternative tools, the exclusions are clear and actionable. Could have been stronger by pointing to named siblings, but the guidance is solid.

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