Steam Inventory Value

Value a Steam inventory

value_steam_inventory

Read-onlyIdempotent

Estimate what a public Steam inventory is worth at current Steam Community Market prices: total value, total after Steam's selling fee, and a subtotal per game (Counter-Strike 2, Dota 2, Team Fortress 2, Rust, PUBG, Steam trading cards and more). Takes up to about a minute. The inventory must be public; nothing is changed on the Steam account.

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": {
      "profile": "<profile>"
    },
    "name": "value_steam_inventory"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	Yes	Steam profile URL (steamcommunity.com/id/... or /profiles/...), a 17-digit SteamID64, or a custom URL name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered; the description still adds real value by stating the roughly one-minute runtime and that nothing is changed on the Steam account. What it does not disclose is behavior on error or rate limiting from the Community Market.

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?

Three short sentences, front-loaded with what is computed and followed by the runtime and the public-inventory requirement. The game enumeration adds useful scope without becoming a wall of text.

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?

With no output schema, the description carries the return-value burden and does so by naming the three result components plus the game coverage. It is nearly complete for a one-parameter read tool; only expected error behavior for private inventories is unstated.

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% and there is a single parameter whose accepted forms (profile URL, 17-digit SteamID64, custom URL name) are fully documented in the schema. The description adds only the constraint that the referenced inventory must be public, which is marginal beyond the schema baseline.

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?

States the specific verb (estimate) and resource (a public Steam inventory's worth) and enumerates the return values: total value, post-fee total, and per-game subtotal. The parenthetical game list makes the scope concrete, so an agent knows exactly what this tool computes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the key precondition (the inventory must be public) and a latency expectation (up to about a minute) that shapes when it's worth calling. No sibling alternatives exist to route against, so the only gap is the absence of explicit failure guidance for private or empty inventories.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Steam Inventory Value tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?