rust.wiki

Executable buy-on-marketplace, sell-on-Steam flips

find_skin_deals

Read-onlyIdempotent

Executable buy-on-marketplace, sell-on-Steam flips. Every skin that can be bought on a third-party marketplace for less than it nets on Steam Community Market right now, as rust.wiki/skins/deals computes it. Per deal: buy_market and buy_price (the cheapest in-stock listing we poll, cents), sell_url (the Steam listing page), the two Steam references bid_gross/bid_net (highest buy order, and what you actually receive after Steam's 15% fee) and ask_gross/ask_net (lowest sell order, same), then for the chosen steam_ref: sell_price (the net proceeds), sell_gross, spread_abs (cents) and spread_pct. Only rows profitable under the chosen reference are returned. A stale buy order above a fresher ask is capped at the ask. Filters combine with AND; search matches the skin name case-insensitively. Marketplace links are not included. Recomputed every ~5 minutes from the marketplace poll.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_skin_deals"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number.
`sort`	No	Best `pct` (spread as % of buy price) or `abs` (spread in cents) first.	pct
`search`	No	Case-insensitive substring of the skin name (or Steam market name).
`category`	No	Only skins of this category.
`per_page`	No	Results per page (max 200).
`max_price`	No	Maximum buy price in cents.
`min_price`	No	Minimum buy price in cents.
`steam_ref`	No	Steam exit price: `buy` = sell instantly into the highest buy order (default), `sell` = list just under the lowest sell order.	buy
`marketplace`	No	Only deals whose cheapest listing is on one of these marketplaces (repeat the parameter).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / marketplace / items / enum

Previous value: -[
-  "Skinport",
-  "CSDealsMarketplace",
-  "DMarket",
-  "RustTM",
-  "CSTrade",
-  "Waxpeer",
-  "LISSkins",
-  "ManncoStore",
-  "SwapGGTrade",
-  "TradeitGG",
-  "RapidSkins",
-  "LootFarm",
-  "RustSkins"
-]New value: +[
+  "Skinport",
+  "CSDealsMarketplace",
+  "DMarket",
+  "RustTM",
+  "CSTrade",
+  "Waxpeer",
+  "LISSkins",
+  "ManncoStore",
+  "SwapGGTrade",
+  "TradeitGG",
+  "RapidSkins",
+  "LootFarm",
+  "RustSkins",
+  "TradeRust"
+]

First observedOct 25, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains the freshness cadence (~5 minutes), the fee treatment (15% Steam fee), the stale-buy-order cap behavior, that only profitable rows are returned, and that marketplace links are omitted. These details materially help an agent understand what the tool will and will not return.

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 dense but front-loaded and appropriately sized for a nine-parameter financial-data tool with no output schema. It could be slightly easier to scan with structure, but almost every clause adds useful semantics.

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?

Given the absence of an output schema, the description does the necessary work by explaining the returned fields, net/gross pricing, spread calculations, freshness, and the stale-order edge case. An agent has enough information to invoke the tool correctly and interpret the result.

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 the input schema already documents all nine parameters well. The description reinforces filtering behavior and explains the chosen `steam_ref` semantics, but most parameter meaning is still carried by the schema, making 3 the appropriate baseline.

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 clearly defines the resource as executable marketplace-to-Steam skin flips and explains the arbitrage logic behind the result set. It is more specific than a generic search tool, but it does not explicitly contrast itself with siblings such as compare_market or get_skin_orderbook.

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?

The use case is strongly implied: find currently profitable buy-low/sell-on-Steam opportunities. However, the description does not explicitly say when to use this tool instead of related siblings like compare_market, get_skin_price, or get_skin_orderbook.

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?