Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam search suggestions

steam_apps_suggest
Read-onlyIdempotent

Searches Steam for a few keywords and returns the app suggestions shown in the search box, helping you find relevant games or software.

Instructions

Get the best matches the Steam search box shows for a few words. Requires query. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Words to look up, e.g. `portal`.
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

C2.9/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds only "Returns a list", which is thin, and omits the conversational sequencing behavior (conversation_id echoed from a prior response, no parallel calls) that the schema flags as important.

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?

Three short sentences, front-loaded with the purpose before constraints and return shape. Nothing is padded, though the second and third sentences carry almost no informational weight.

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 six-parameter read tool with no output schema, the description covers purpose and return type but says nothing about what each suggestion contains or how many are returned. It also under-reports requirements by naming only `query` while context and llm_model are also required.

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?

Schema description coverage is 100%, so every parameter including country, language, llm_model, and conversation_id is already documented. The description adds no syntax, defaults, or meaning beyond restating that query is required, which the schema already declares, so baseline 3 applies.

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?

The description names a specific verb and resource: 'best matches the Steam search box shows for a few words', which reads as autocomplete/typeahead suggestions rather than a full catalog search. That is enough for an agent to distinguish it conceptually from a general search, though it never names a sibling like steam_apps_search to make the contrast explicit.

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?

"Requires `query`" is a parameter constraint, not usage guidance. There is no statement of when to prefer this over steam_apps_search or steam_apps_browse, and no note on when suggestions are the right tool versus fetching app details.

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