Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_prices_search

Search the steam-prices dataset. Searches the daily price time series for priced games (one document per appid × day; integer cents). Pair app_id with sort=date_desc for a game's price history, or pass date for one day's snapshot.

Instructions

Search the steam-prices dataset. Searches the daily price time series for priced games (one document per appid × day; integer cents). Pair app_id with sort=date_desc for a game's price history, or pass date for one day's snapshot. Sort enum: date_desc (default), date_asc, price_asc, price_desc, discount_desc. 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
dateNoSnapshot date filter yyyy-MM-dd
pageNoPage number, defaults to 1
sortNoSort enum: date_desc, date_asc, price_asc, price_desc, discount_desc
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: +[
+  "date_desc",
+  "date_asc",
+  "price_asc",
+  "price_desc",
+  "discount_desc"
+]
  2. Added
  3. Removedv1.6.0
  4. Addedv1.5.0

TDQS

A4.4/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, and it does well: it discloses the credit cost model (1 credit/record, minimum 2, worked examples), the record granularity, and the integer-cents representation. It leaves return-field shape and pagination behavior unstated.

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?

Front-loaded with the core purpose, then usage patterns, then sort enum, then billing. Every sentence carries information an agent needs and nothing is redundant.

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 is the sole carrier of behavior, and it covers data model, cost, defaults, and query patterns adequately. It does not describe what fields a returned document contains, which is the remaining minor gap.

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%, so the baseline is 3, but the description adds real semantic value: it explains the app_id + sort=date_desc combination (price history) and the date parameter (single-day snapshot), and confirms date_desc as the effective default. This goes beyond the field-level schema descriptions.

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 (Search) plus the exact resource (the steam-prices dataset) and immediately pins down the underlying data model: one document per appid × day with integer cents. This distinguishes it from sibling dataset searches like datasets_steam_games_search without requiring the 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?

Gives two concrete invocation patterns — 'pair app_id with sort=date_desc' for a history and 'pass date' for a daily snapshot — which is explicit when-to-use guidance. It stops short of naming an alternative tool to use instead when the user wants static game metadata rather than prices.

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