Skip to main content
Glama
Sign In

rust.wiki

by wiki.rust
OverviewDiscussionsAdmin

One Workshop artist: every accepted Rust skin they made and what it's worth

get_skin_creator
Read-onlyIdempotent

One Workshop artist: every accepted Rust skin they made and what it's worth. The data behind https://rust.wiki/creators/: the artist's skins with prices (USD cents), count, total and average value, top skin, first and last release, and the split by item, collection and category.

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": {
      "steamid": "<steamid>"
    },
    "name": "get_skin_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
steamidYesThe artist's SteamID64 (from /creators or a skin's creator).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real content: prices in USD cents, count, total and average value, top skin, first/last release, and splits by item, collection and category. It stops short of noting behavior for an unknown or non-artist SteamID.

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?

Two sentences, fully front-loaded: identity and scope first, then the field inventory. The long enumeration of returned fields is dense but every item is informative and none of it is filler.

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?

There is no output schema, so the description has to carry the return shape, and it does so with a concrete field list for a single-parameter tool. The main residual gap is error/edge-case behavior (invalid or unknown SteamID) and any freshness caveats for pricing.

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

Parameters4/5

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

Schema coverage is 100% and the only parameter carried a pattern, example and description, so baseline is 3. The description goes slightly beyond by explaining where the SteamID64 comes from (the /creators page or a skin's creator), which helps an agent obtain a valid value.

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 specific resource and scope: a single Workshop artist's accepted skins plus valuation data, with the backing URL pattern given. 'One Workshop artist' implicitly contrasts with the sibling list_skin_creators and the single-skin get_skin, but no alternative 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?

Usage is only implied: the phrasing plus the '/creators/<steamid>' path makes clear this is the per-creator profile lookup. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as list_skin_creators for discovery.

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

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