Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_achievements_search

Search Steam achievement unlock percentages per game. Filter by app ID and sort by rarity or rank to find global achievement data.

Instructions

Search steam-achievements dataset. Searches per-game global achievement unlock percentages (one document per appid × achievement). Pass app_id to list a game's achievements. Sort enum: percent_desc (most-unlocked first, default), percent_asc (rarest first), rank_asc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, defaults to 1
sortNoSort enum: percent_desc, percent_asc, rank_asc
app_idNoExact Steam app id filter
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "percent_desc",
+  "percent_asc",
+  "rank_asc"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the data granularity (one document per appid × achievement), the default sort, and the effect of app_id. However, it doesn't disclose pagination behavior, rate limits, or what fields are returned per document. The description adds some behavioral context but not rich detail.

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 with no fluff. The core purpose is front-loaded, and the sort enum explanation is compact. Every sentence earns its place, though the sort enum is partially repeated in the schema.

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

Completeness3/5

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

For a search tool with 4 optional parameters and no output schema, the description covers the main usage patterns (filtering by app_id, sorting). It doesn't explain the return format or pagination constraints beyond what the schema states, but the tool is simple enough that this is a minor gap. The page_size constraint is in the schema, not the description, which is acceptable.

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 schema already documents all four parameters. The description adds meaning for `app_id` (list a game's achievements) and the sort enum (percent_desc = most-unlocked first, percent_asc = rarest first, rank_asc), which goes slightly beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description states a specific verb ('Search') and resource ('steam-achievements dataset'), and clarifies the data model: one document per appid × achievement, with per-game global achievement unlock percentages. It distinguishes itself from sibling tools like steam_achievements, steam_app, and datasets_steam_games_search by focusing on achievement unlock percentages, though it doesn't explicitly name a sibling alternative.

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 gives clear context: pass `app_id` to list a game's achievements, and explains the sort enum values with their meanings. It doesn't explicitly state when not to use this tool or name alternatives, but the usage context is clear enough for an agent to select it appropriately among the many steam-related siblings.

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