Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

datasets_steam_prices_facets

Read-only

Return up to 50 facet buckets with counts for one Steam price-history field using the filters from datasets_steam_prices_search. facet accepts app_id or snapshot_date; page and page_size do not change counts; sort is validated but does not change bucket order. Supplying date scopes the snapshot-date counts to that date. Use datasets_steam_prices_search to find daily price records.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "facet": "<facet>"
    },
    "name": "datasets_steam_prices_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional snapshot date filter, yyyy-MM-dd.
pageNoResult page number, 1-based, default 1; page times page_size must not exceed 10000.
sortNoOptional sort order. Allowed values: date_desc (default), date_asc, price_asc, price_desc, discount_desc.
facetYesrequired,Required facet. Allowed values: app_id, snapshot_date.
app_idNoOptional exact Steam app id filter; pair with sort=date_desc for an app's price history.
page_sizeNoPage size, default 20, max 100; page times page_size must not exceed 10000.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses several non-obvious behaviors: a hard cap of 50 buckets, that page/page_size do not change counts, that sort is validated but does not reorder buckets, and that supplying date scopes snapshot-date counts. These are exactly the quirks an agent would otherwise guess wrong about.

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?

Five short sentences, front-loaded with the output shape and the facet constraint, followed by the behavioral caveats and the sibling redirect. No filler and nothing buried.

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

Completeness5/5

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

An output schema exists so return structure need not be explained; the description covers the remaining unknowns — bucket cap, count invariance to paging/sorting, and date scoping. Nothing needed to invoke it correctly is missing.

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 the baseline is 3. The description still adds semantic value the schema does not convey: which facet values exist (duplicated, but framed as guidance), that page/page_size are count-neutral, and that date narrows snapshot_date counts specifically.

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?

The description states a specific verb and resource — 'Return up to 50 facet buckets with counts for one Steam price-history field' — and immediately names the field values (app_id, snapshot_date). It is unambiguously distinguishable from the sibling search tool, which returns records rather than counts.

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?

It routes the agent explicitly: 'Use datasets_steam_prices_search to find daily price records,' clarifying that this tool is for aggregation, not record retrieval. It also tells the agent that pagination and sort are pointless for counts. It lacks an explicit 'do not use this when…' exclusion, so a 4 rather than 5.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources