Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_games_facets

Facet the Steam games dataset by genre, developer, price tier, or review score to get aggregated counts for distribution analysis.

Instructions

Facet the Steam games dataset. Returns terms aggregation counts for the Steam games dataset. Facet enum: type, developer, publisher, genres, categories, tags, primary_tag, price_tier, review_tier, owners_bucket, release_year, run_id, is_free, coming_soon, platform_windows, platform_mac, platform_linux. price_tier enum: free, under5, 5to15, 15to30, 30to60, over60. review_tier enum: overwhelmingly_positive, very_positive, positive, mostly_positive, mixed, mostly_negative, negative, very_negative, overwhelmingly_negative, insufficient.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name, developer and publisher, max 256 characters
macNoFilter by macOS support
tagNoExact community-tag filter (e.g. Roguelike, Cozy), max 128 characters
typeNoExact storefront type filter, max 128 characters
facetYesFacet enum: type, developer, publisher, genres, categories, tags, primary_tag, price_tier, review_tier, owners_bucket, release_year, run_id, is_free, coming_soon, platform_windows, platform_mac, platform_linux
genreNoExact genre filter, max 128 characters
linuxNoFilter by Linux support
run_idNoExact crawl run-id filter, max 128 characters
is_freeNoFilter by free-to-play flag
min_ccuNoMinimum peak concurrent users yesterday
on_saleNoFilter by titles currently discounted (discount_pct > 0)
windowsNoFilter by Windows support
categoryNoExact store category filter, max 128 characters
developerNoExact developer filter, max 128 characters
publisherNoExact publisher filter, max 128 characters
min_ownersNoMinimum estimated owners (SteamSpy owners midpoint)
price_tierNoPrice-tier enum: free, under5, 5to15, 15to30, 30to60, over60
review_tierNoReview-tier enum: overwhelmingly_positive, very_positive, positive, mostly_positive, mixed, mostly_negative, negative, very_negative, overwhelmingly_negative, insufficient
min_positiveNoMinimum positive review count
owners_bucketNoExact SteamSpy owners-range bucket filter, max 128 characters
min_metacriticNoMinimum Metacritic score, 0 through 100
max_price_centsNoMaximum current price in cents
min_price_centsNoMinimum current price in cents
max_release_yearNoMaximum release year
min_release_yearNoMinimum release year
min_review_scoreNoMinimum positive-review ratio, 0 through 1
min_total_reviewsNoMinimum total review count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / facet / enum
      Added value: +[
+  "type",
+  "developer",
+  "publisher",
+  "genres",
+  "categories",
+  "tags",
+  "primary_tag",
+  "price_tier",
+  "review_tier",
+  "owners_bucket",
+  "release_year",
+  "run_id",
+  "is_free",
+  "coming_soon",
+  "platform_windows",
+  "platform_mac",
+  "platform_linux"
+]
    • addedInput schema / properties / price_tier / enum
      Added value: +[
+  "free",
+  "under5",
+  "5to15",
+  "15to30",
+  "30to60",
+  "over60"
+]
    • addedInput schema / properties / review_tier / enum
      Added value: +[
+  "overwhelmingly_positive",
+  "very_positive",
+  "positive",
+  "mostly_positive",
+  "mixed",
+  "mostly_negative",
+  "negative",
+  "very_negative",
+  "overwhelmingly_negative",
+  "insufficient"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior ('Returns terms aggregation counts') but does not explain response structure, pagination, limits, or whether the counts are capped. For an unannotated tool this is a significant gap beyond the bare minimum.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are reasonably short but repeat 'Steam games dataset' and could be merged. The third sentence exhaustively repeats enum values that are already in the input schema, so a large portion of the description does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 27 parameters, no annotations, and no output schema, the description is underspecified. It explains that counts are returned but not the shape of the response, count limits, or how filters combine. An agent could call it correctly for the required facet parameter, but would be guessing about the return contract.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's enum lists merely duplicate the schema's existing enum definitions and add no new meaning. All 27 parameters are already documented in the schema, so the description contributes nothing extra.

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?

States a clear verb ('Facet') and resource ('Steam games dataset'), and explains the result as 'terms aggregation counts,' which separates it from sibling tools like datasets_steam_games_search and datasets_steam_games_item. However, it does not explicitly contrast with those siblings, so it stops short of a 5 on differentiation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool instead of datasets_steam_games_search or datasets_steam_games_item. There is no mention of prerequisites, typical use cases, or when filtering/searching would be preferable. The description is entirely neutral and leaves selection to inference.

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

Deploy Server

Other Tools