Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam Hardware Survey

steam_hardware_survey_get
Read-onlyIdempotent

Fetch the monthly Steam Hardware and Software Survey to retrieve OS, graphics card, processor, and memory distribution data for market or compatibility analysis.

Instructions

Get the monthly Steam Hardware and Software Survey: operating systems, graphics cards, processors, memory and more.

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_hardware_survey_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior, so the safety bar is largely met. The description adds the useful cadence signal 'monthly' but says nothing about whether historical months are retrievable, how large the payload is, or whether any auth/quota applies.

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?

A single front-loaded sentence with no filler. It is appropriately short for a no-argument read tool, though the trailing 'and more' is slightly vague padding.

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 simple no-output-schema read tool, stating the subject matter is mostly sufficient, but it omits whether the result is the current month only, how categories are keyed in the response, and confirmation that it takes no data-selection arguments.

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?

All three parameters are fully documented in the schema (context, llm_model, conversation_id), so the 100% coverage baseline of 3 applies. The description adds nothing about them, and notably there is no parameter for selecting a month or category, which the description does not clarify.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource (get / Steam Hardware and Software Survey) plus an enumeration of the payload (OS, GPUs, CPUs, memory). It reads clearly as a survey/metrics tool, distinct from the app-, review-, and market-oriented siblings, though it never explicitly contrasts with them.

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 when-to-use or when-not-to-use guidance and no alternatives named. The only implicit cue is the word 'monthly', leaving the agent to infer when a hardware-distribution lookup is the right call.

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