get_armory_roiList the current Counter-Strike 2 Armory rotation tiles with their credit cost and expected value, or get one tile with every item it can produce and the rarity weighting. Use this to compare what Armory credits are worth across the current rotation.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Armory tile slug. When set, returns that tile with its full item list instead of the rotation overview. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses two modes (overview vs. detail) and what each returns (credit cost, expected value, item list, rarity weighting). It implies read-only behavior but doesn't explicitly state no side effects or authentication requirements. This is adequate for a listing tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences: first states the core functionality, second explains the optional parameter, third gives a use case. No redundant words. Efficient and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one optional parameter, no output schema, and no annotations, the description covers the tool's behavior adequately. It explains both modes and the use case. Could mention return format or data freshness, but not essential.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one optional parameter 'slug' with a description that matches the tool's behavior. Schema coverage is 100%, so the description does not need to add extra parameter info. The description reinforces the parameter's effect, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists Armory rotation tiles with credit cost and expected value, or returns a single tile with full item list and rarity weighting. This distinguishes it from sibling tools like browse_cases or get_case_roi_ranking.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a use case: 'compare what Armory credits are worth across the current rotation.' It implies this is for assessing value, though it doesn't explicitly say when not to use it. The sibling tools are distinct so confusion is unlikely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of CS2 cosmetics: browsing categories, searching, getting details, and ROI calculations. There is no overlap as browse/get/search verbs are clearly separated by resource type.
All tools follow a consistent verb_noun pattern (e.g., browse_bargains, get_case_roi_ranking, search_skins), using underscores and clear action words.
With 9 tools, the server covers the core functionality of browsing, searching, and analyzing CS2 skins and containers without being overly large or sparse.
The tool set covers browsing, searching, detail retrieval, and ROI analysis for cases and armory. A minor gap is the lack of user account operations or direct trading, but the server's scope is well-defined.