browse_bargainsFind cheap Counter-Strike 2 skins grouped into price-threshold pages, for example AK-47 skins under 10 dollars or the cheapest knives. Without a slug it lists every available page; with a slug it returns the skins on that page with their current cheapest listing price.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Bargain page slug, for example "ak-47-skins-under-10-dollars" or "cheapest-knives". Omit to list every available page. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Describes behavior (grouping, listing pages, returning cheapest price) but does not disclose non-obvious traits like data freshness or potential API limits. Adequate for a simple read operation.
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?
Two sentences with zero waste. Front-loaded with main purpose, then conditional behavior. Every sentence adds value.
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?
Describes input/output well for a simple tool without output schema. Could clarify what 'every available page' means (e.g., page names/links), but sufficient for agent invocation.
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?
Input schema has 100% coverage with a solid description for slug. The description adds practical examples of slug values, enhancing usability beyond the schema's formal definition.
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?
Specific verb 'browse' with resource 'cheap CS2 skins' and clear grouping into price-threshold pages. Examples like 'AK-47 skins under 10 dollars' distinguish from sibling tools like browse_cases and search_skins.
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?
Explains conditional behavior with and without slug, but does not explicitly state when to use this tool versus sibling tools like search_skins for general searches. Implicitly clear given the focus on cheap skins.
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.