Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

datasets_steam_prices_item

Read-only

Fetch one stored Steam price snapshot by the exact app_id and snapshot_date returned by datasets_steam_prices_search. Dates use yyyy-MM-dd; absent records return 404. Use datasets_steam_prices_search to find price history.

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_idYesRequired Steam app id returned by datasets_steam_prices_search.
snapshot_dateYesRequired snapshot_date returned by datasets_steam_prices_search.

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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context: dates use yyyy-MM-dd and absent records return 404, which materially helps an agent avoid and interpret failures.

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?

Three tight sentences, front-loaded with the core action and followed by the date/error behavior and sibling routing. Every sentence contributes useful information with no waste.

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?

For a simple two-parameter lookup with a 100% schema description coverage, an output schema, and annotations covering safety, the description supplies the key remaining context: input provenance, date format, 404 behavior, and the search alternative.

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 adds meaning beyond the schema by specifying the yyyy-MM-dd date format and emphasizing that app_id and snapshot_date must be exact values returned by the search tool.

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 and resource: 'Fetch one stored Steam price snapshot' by exact app_id and snapshot_date. This clearly distinguishes it from the search sibling and tells an agent exactly what the tool returns.

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?

Explicitly routes the agent to datasets_steam_prices_search for finding price history, and states that this tool requires exact identifiers returned by that search. Clear context, though it does not spell out an explicit when-not condition beyond the implied retrieval-after-search flow.

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