Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_category

Browse a Steam store category by numeric tag id or name to fetch catalog entries with weighted community tags, review scores, credits, release date, platforms, and price.

Instructions

Browse a store category (tag) with weighted community tags. Returns a catalog slice for a community tag / category, carrying each item's WEIGHTED community tags, review-score breakdown, developer/publisher credits, release date, platforms and price. The slug is a numeric tag id or a tag name (case- and separator-insensitive, e.g. rogue_like); resolve ids via /steam/tags/list. Ordering is Steam's default relevance — for sorted or os/price-faceted browse use /steam/tags.

Input Schema

NameRequiredDescriptionDefault
lNoSteam store language name
ccNoStore country code (ISO, selects currency)
freeNoOnly free titles
slugYesCommunity tag id (numeric) or tag name slug
countNoResults per page (max 100)
startNoResult offset for pagination
released_onlyNoOnly already-released titles
coming_soon_onlyNoOnly unreleased / coming-soon titles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the ordering behavior (Steam default relevance), the shape of each item (weighted tags, review-score breakdown, credits, release date, platforms, price), and the flexible slug format. It doesn't mention pagination limits or rate/auth constraints, but covers the operationally important traits.

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?

Three sentences, front-loaded with the core purpose and return shape, then slug mechanics, then ordering/routing. Dense but every sentence adds information; no filler or restatement of the title.

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 annotations, the description supplies the return-shape overview, ordering behavior, slug semantics, and sibling routing needed to call it correctly. Only minor gaps remain (pagination behavior, auth) in what is otherwise a complete picture for an 8-parameter browse 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?

Schema coverage is already 100%, but the description adds real meaning for the required slug parameter: numeric tag id or tag name, case- and separator-insensitive with a concrete example (rogue_like), and a resolution path. That goes beyond the schema's terse 'Community tag id or tag name slug'.

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?

States a specific verb and resource ('Browse a store category (tag)') and immediately differentiates itself from the sibling browse endpoint by describing what it returns versus what /steam/tags offers. An agent can distinguish this from steam_tags, steam_tags_list, and steam_search without opening any schema.

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?

Explicitly routes the agent: default relevance ordering here, and 'for sorted or os/price-faceted browse use /steam/tags', plus 'resolve ids via /steam/tags/list'. It gives clear when-to-use and an alternative, though the alternatives are referenced as paths rather than tool names, which adds a small mapping step for the agent.

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