rust.wiki

Current Rust Twitch and Kick drops

get_twitch_drops

Read-onlyIdempotent

Current Rust Twitch and Kick drops. The live drops campaigns (Twitch and Kick: round, dates, general and streamer drops with the skin each one gives), the most valuable drop skins ever by Steam price, and past rounds - the data behind rust.wiki/drops.

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": "get_twitch_drops"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by enumerating the three data categories returned (live campaigns, top drop skins, past rounds) and noting the source as the data behind rust.wiki/drops. It does not mention freshness or update frequency, which is a minor gap for a 'current' dataset.

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 front-loads the purpose in the first sentence and uses the second sentence to enumerate data categories. The parenthetical list is dense but every clause adds useful scope information; there is no filler, though the nested list slightly reduces readability.

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 and no parameters, the description carries the burden of explaining return content. It does so adequately by naming the three data categories and the source URL. It could be more complete by mentioning response format or data freshness, but the essential scope is clear.

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?

The tool takes zero parameters, so parameter semantics are not applicable and the baseline score is 4. No additional parameter meaning is needed or expected.

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 identifies the resource: current Rust Twitch and Kick drops, including live campaigns, most valuable drop skins by Steam price, and past rounds. It is highly specific about the data returned, though it is phrased as a noun phrase rather than a verb-led statement. No sibling tool covers drops, so differentiation is not needed.

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 content description: an agent can infer this is the tool for Twitch/Kick drop campaign information. However, there is no explicit guidance on when to use this versus related tools like get_skin_price or get_market_movers, nor any stated exclusions.

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?