Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Steam Community Market

steam_market_items_search
Read-onlyIdempotent

Search Steam Community Market items by name or app ID and return their lowest prices, with paginated results for browsing listings.

Instructions

Search items on the Steam Community Market with their lowest price. Optional inputs: query, appId and page. Returns a list (use page when paginated).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based). Default: 1.
appIdNoOnly items of this app, e.g. `730` for Counter-Strike 2.
queryNoWords to search item names for, e.g. `ak-47`.
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.4/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 the safety profile is covered. The description adds that results include lowest price and are paginated, which is useful, but says nothing about rate limits, result caps, or ordering.

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?

Two short sentences, front-loaded with the core action and resource, with no wasted wording. The parenthetical about pagination is slightly terse but earns its place.

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 tool with two required meta-parameters (context, llm_model) and a conversation_id, the description says nothing about those required fields or the conversation flow. It does briefly note the return shape, which helps since there is no output schema, but overall it is only minimally complete.

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 all six parameters are already documented in the schema. The description only restates the three optional inputs without adding format or semantics beyond what the schema provides, 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?

States a specific verb and resource: 'Search items on the Steam Community Market with their lowest price.' An agent can tell it apart from steam_market_item_price_get (single price lookup) by the search/list framing, though no sibling is named explicitly.

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?

Mentions that query, appId and page are optional and hints 'use page when paginated', which implies usage. But it gives no explicit when-to-use vs when-not guidance or routing to alternatives like steam_market_item_price_get.

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