Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_prices_item

Retrieve one stored daily Steam price record by app ID and snapshot date to check historical pricing for a specific game.

Instructions

Get one stored Steam price record. Retrieves one daily price row using appid and snapshot_date from datasets_steam_prices_search.

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": {
      "app_id": "<app_id>",
      "snapshot_date": "<snapshot_date>"
    },
    "name": "datasets_steam_prices_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesSteam app id
snapshot_dateYesSnapshot date, yyyy-MM-dd

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully signals a single-row point lookup on stored data rather than a live quote, but says nothing about behavior when no row matches the date, whether a record can be missing, or error/empty semantics for a mutation-free lookup.

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?

Two tight sentences with the resource and scope front-loaded and the sibling reference placed after, so an agent gets the key routing fact immediately. Nothing is redundant or padded.

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 simple two-parameter, required-only lookup with no output schema and no annotations, the definition covers what the tool returns at a high level (one daily price row) and how to source the keys. It could say slightly more about missing-record behavior, but nothing essential to invoking it is absent.

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% and the format for `snapshot_date` (yyyy-MM-dd) is already documented in the schema, so the description adds little per-parameter detail. Its one contribution is provenance: which tool supplies the valid `appid`/`snapshot_date` values.

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 and resource ('Get one stored Steam price record') and narrows it to a single daily price row, which clearly separates it from the bulk search sibling it names. The only blemish is the minor identifier mismatch: it refers to `appid` while the schema parameter is `app_id`, which could momentarily confuse an agent.

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 gives real routing context by saying the `appid` and `snapshot_date` values come from `datasets_steam_prices_search`, implying search-then-fetch workflow. It stops short of stating when not to use it (e.g., that it returns only previously stored snapshots, not live or arbitrary-range data).

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