Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_achievements_search

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.

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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

A4.3/5.0
Behavior4/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 an important non-obvious trait—the billing model (1 credit per record, min 2, empty result costs 2, 100 records cost 100)—which is genuinely valuable and not derivable from schema. It stops short of stating read-only status or rate limits, so not a 5.

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?

Four tight sentences, front-loaded with dataset scope before sort and billing details. Each sentence carries information; the sort enum is restated but with added explanation, which is mostly justified.

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?

For a search tool with no output schema, the description covers scope, filtering, sorting and billing. Pagination limits live in the schema, so the definition is largely complete, though it could note read-only behavior for full transparency.

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 100%, so baseline is 3. The description adds real meaning beyond the schema by explaining the sort enum semantics ('percent_desc' = most-unlocked first and is the default, 'percent_asc' = rarest first) and the app_id listing behavior, going beyond the bare enum list.

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+resource ('Search steam-achievements dataset') and immediately clarifies the granularity ('one document per appid × achievement'). This content-level specificity clearly distinguishes it from sibling steam datasets such as datasets_steam_games_search or datasets_steam_prices_search.

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?

Gives concrete usage context: 'Pass app_id to list a game's achievements,' which tells the agent how to get a specific game's data. It does not name an alternative tool or state when NOT to use this, so it stops short of the explicit when/when-not/alternatives bar.

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