Steam-MCP

get_news_for_app

Retrieve news articles for any Steam application by providing its App ID. Choose the number of items and maximum character length per article.

Instructions

Get the latest news for a Steam app.

No API key required.

Return Format

{"success": bool, "message": str, "data": {"appid": int, "newsitems": [...]}}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "get_news_for_app"
  }
}

Input Schema

Name	Required	Description
`app_id`	Yes	Steam App ID (e.g. 440).
`count`	No	Number of news items to return.
`max_length`	No	Max characters per news item.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the return format and notes no API key requirement, but does not mention potential side effects, rate limits, or data freshness. The description adds value but could be more comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the core purpose. The return format is clearly presented. Slightly more concise could include removing the 'Return Format' header, but overall efficient.

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?

Given the tool's simplicity (3 parameters, 1 required, output schema described), the description is fairly complete: it states the purpose, has no auth complexity, and shows the response structure. Lacks details on error handling or pagination, but sufficient for basic use.

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 input schema covers 100% of parameters with descriptions. The description only reiterates the purpose and return format, adding no additional semantics beyond what the schema provides. Baseline score of 3 is appropriate.

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 'Get the latest news for a Steam app,' which is a specific verb+resource combination. This distinguishes it from sibling tools like 'get_app_details' or 'get_friend_list' that serve different purposes.

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 notes 'No API key required,' which is a helpful usage condition, but it does not explicitly state when to use this tool versus alternatives or provide exclusion criteria. The implied usage is for fetching news, but no direct comparison to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server