rust.wiki

Full Steam order book for one skin

get_skin_orderbook

Read-onlyIdempotent

Full Steam order book for one skin. Steam Community Market's current order book for the skin, straight from our scraper's latest snapshot: lowest_sell_order and highest_buy_order (cents; null when that side is empty), sell_order_count and buy_order_count, the COMPLETE sell_orders and buy_orders depth ladders as [{price, quantity}, ...] best price first (every level Steam publishes, not a top-N cut), and fetched_at, when the snapshot was taken. The headline ask is refreshed by a market-wide sweep every ~12 minutes; the depth ladders come from the per-item rotation (every few hours), so they can trail it slightly. 404 when the skin has no Steam order book (unmarketable items). Not cached: this is one indexed row.

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": {
      "itemdefid": "<itemdefid>"
    },
    "name": "get_skin_orderbook"
  }
}

Input Schema

Name	Required	Description	Default
`itemdefid`	Yes	The skin's item definition id.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that prices are in cents, null means an empty side, a 404 signals unmarketable items, and that the result is not cached. It also explains the two-tier refresh cadence (headline ~12 min market sweep vs. depth ladders from a per-item rotation every few hours) and that ladders can trail — precisely the nuance an agent needs to interpret the data.

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?

Front-loaded with the purpose, then a dense but well-organized enumeration of returned fields, followed by freshness and error behavior. It is long for a one-parameter read tool, but nearly every clause adds operational value rather than repeating the schema.

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

Completeness5/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 fully documents the return shape (lowest_sell_order, highest_buy_order, order counts, full ladders as {price, quantity}), units, null semantics, freshness asymmetry, and the 404 case. Nothing an agent needs to call or interpret this tool correctly is missing.

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 coverage is 100% for the single itemdefid parameter, so the schema already carries the semantics and a baseline 3 is appropriate. The description adds the scoping idea ('one skin') but no format or lookup guidance beyond what the schema states.

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 resource and scope: the full Steam order book for one skin, with the explicit contrast that the depth ladders include 'every level Steam publishes, not a top-N cut.' That separates it from price-only siblings like get_skin_price, but no sibling is named directly, so differentiation is implied rather than stated.

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?

Usage is implied by the emphasis on completeness (full ladders vs. a headline ask) and the freshness note, which helps an agent decide when depth matters. However, it never says 'use get_skin_price for the headline price' or otherwise routes the agent among the many skin/market siblings, and there are no explicit when-not conditions.

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

All rust.wiki 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?