SkinGrind

Browse CS2 collections

browse_collections

List Counter-Strike 2 collections, or get one collection with its contents. Optionally includes the collection Trade Up map: which rarity tiers exist in the collection and what each tier can produce. That map is catalog contract math, not scanner output.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number.
`slug`	No	Collection slug. When set, returns that collection with its contents instead of the list.
`sort`	No	List ordering: newest, oldest or name. For a single collection the contents order: rarity, name, price_asc or price_desc.
`type`	No	Filter the list by what the collection contains.
`search`	No	Free-text collection name search.
`per_page`	No	Results per page, 1 to 25.
`include_tradeup_map`	No	Only with slug. Adds the collection Trade Up map showing each rarity tier and its possible outputs.

TDQS

A4.4/5.0

Behavior4/5

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

With empty annotations, the description carries full burden. It discloses that the trade-up map is based on catalog contract math, not scanner output, which is a key behavioral trait. It does not cover response caching or real-time status, but the disclosed nuance adds value.

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?

The description is two sentences with no fluff. Each sentence provides essential information: purpose and optional feature. It is front-loaded with the primary action.

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?

Given the complexity (7 parameters, no output schema, no annotations), the description covers the core modes and optional feature. It does not detail return format or pagination, but the schema covers parameter details. Reasonably complete for a browsing tool.

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?

All parameters have schema descriptions (100% coverage). The description adds context beyond schema for include_tradeup_map by explaining its content. This extra meaning justifies a score above baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists collections or retrieves one with contents. It uses specific verbs and resource, and the title reinforces the purpose. It distinguishes from siblings like browse_cases by focusing on collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the trade-up map feature and implies the two modes (list vs single). However, it does not explicitly compare with alternative tools like get_tradeup_preview or search_skins, so guidance is slightly incomplete.

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

All SkinGrind tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

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.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., browse_bargains, get_case_roi_ranking, search_skins), using underscores and clear action words.

Tool Count5/5

With 9 tools, the server covers the core functionality of browsing, searching, and analyzing CS2 skins and containers without being overly large or sparse.

Completeness4/5

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.

Resources

Need Help?