Skip to main content
Glama
Sign In
steam-mcp

steam-mcp

by Praeses0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

workshop

Access Steam user-generated content. List items, fetch statistics, or search by query and appid to find what you need.

Instructions

List workshop items, stats, or search

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": {
      "action": "<action>"
    },
    "name": "workshop"
  }
}

Input Schema

NameRequiredDescriptionDefault
appidNo
countNo
queryNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits itself. It states the tool can list, fetch stats, or search, but does not say whether the operations are read-only, whether an appid context is required, or what side effects or limitations exist.

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 very short and front-loaded with the core operation, containing no filler or redundancy. It sacrifices completeness for brevity, but as a structural matter it is concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, zero schema descriptions, and no usage guidance, this single fragment leaves the agent with almost no context needed to invoke the tool correctly. It does not explain parameter relationships, return values, or action-specific requirements.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions workshop items and the three actions, loosely echoing the action enum, but it adds no meaning for appid, count, or query. This is inadequate for a 4-parameter tool with no schema descriptions.

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 clear resource ('workshop items') and three operations (list, stats, search) that map directly to the action enum. This differentiates it from siblings like games, library, or proton, though the phrasing is telegraphic and not fully grammatical.

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?

There is no guidance on when to use workshop versus a sibling tool, nor any direction on which action or parameters fit common scenarios. The operation names imply usage but the description leaves the selection criteria entirely to the agent.

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