Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_app_news

Read-only

Fetch recent news, patch notes, and announcements for a Steam game using its app ID. Specify item count and output format (markdown or JSON).

Instructions

Get recent news/update posts for a game (patch notes, announcements).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.18.0
    • removedInput schema / $defs / AppNewsInput / properties / appid / title
      Removed value: -"Appid"
    • removedInput schema / $defs / AppNewsInput / properties / count / title
      Removed value: -"Count"
    • removedInput schema / $defs / AppNewsInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / AppNewsInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / AppNewsInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / AppNewsInput / title
      Removed value: -"AppNewsInput"
    • 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_newsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_app_newsOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds minor context by specifying the type of content (patch notes, announcements). However, it does not disclose potential rate limits, error behavior, or the fact that response_format can be json/markdown. With annotations covering safety, a 3 is appropriate.

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, focused sentence with no filler. It front-loads the core action and resource, and the parenthetical examples add value without bloat.

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 tool is relatively simple with one required parameter, but the description omits usage guidance and parameter semantics. There is no output schema to clarify return values. While the read-only annotation covers safety, an agent would benefit from knowing the response_format options or typical use cases. The description is functional but not fully complete for optimal tool selection.

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?

Schema description coverage is 0%, meaning the description should compensate for parameter explanations. It does not mention appid, count, or response_format at all. The schema itself provides only minimal descriptions (e.g., 'Steam application (game) ID.'), so the agent gets no additional clarity from the description.

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 action (get), the resource (recent news/update posts for a game), and provides concrete examples (patch notes, announcements). It differentiates from sibling tools like steam_get_app_details or steam_get_app_reviews by focusing specifically on news content.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. There is no mention of 'use this for news/updates, use steam_get_app_details for metadata' or any situational context. The agent must infer from the name and description alone.

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