Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam featured items

steam_featured_get
Read-onlyIdempotent

Fetches Steam store front-page specials, upcoming games, top sellers, and new releases, with optional country and language settings for localized pricing and text.

Instructions

Get the specials, upcoming games, top sellers and new releases on the Steam store front page. Optional inputs: country and language.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_featured_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoCountry the prices are shown for, as an ISO 3166-1 alpha-2 code. Default: `US`.
languageNoLanguage of the text: a Steam language name or short code such as `german` or `de`. Default: `en`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that country/language affect the returned content, but does not mention the conversation_id handshake or rate limiting, which are disclosed only in the schema.

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?

Two short sentences, front-loaded with the resource and its contents, then the optional inputs. No filler.

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?

Complete for a read-only, no-output-schema listing tool whose annotations cover safety and whose schema covers every parameter. A note on response shape or pagination would round it out, but nothing needed to invoke it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by noting country and language are optional and that they change localized pricing and text, which the schema documents per-field but the description frames as the meaningful knobs.

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?

Specific verb and resource: retrieves the store front page's specials, upcoming games, top sellers and new releases. This distinguishes it clearly from siblings like steam_app_get or steam_charts_list, which target individual apps or charts.

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 usage (browsing the Steam front page) but names no when-to-use conditions or alternatives such as steam_apps_browse for deeper browsing. No exclusions are stated.

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