Crawlora MCP

datasets_steam_charts_item

Read-only

Fetch one stored Steam chart row by its exact chart_uid from datasets_steam_charts_search. The id identifies a chart, country, date, and rank; absent ids return 404. Use datasets_steam_charts_search to find chart 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": {
      "chart_uid": "<chart_uid>"
    },
    "name": "datasets_steam_charts_item"
  }
}

Input Schema

Name	Required	Description	Default
`chart_uid`	Yes	Required exact chart_uid returned by datasets_steam_charts_search.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

readOnlyHint and openWorldHint already declare the safety profile, so the description only needs to add context. It adds two useful traits: absent ids return 404, and the uid encodes chart, country, date, and rank. It doesn't discuss rate limits or what happens on malformed ids, but the annotation bar is already met.

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 short sentences, front-loaded with the verb and resource, followed by failure behavior and the alternative tool. No filler and nothing repeated from the schema.

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?

The output schema exists, so return values need no explanation, and the single parameter is fully covered. The description supplies the lookup prerequisite and error behavior, which is everything an agent needs to call this correctly.

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 goes beyond the schema by explaining what the chart_uid semantically represents (a chart/country/date/rank tuple) and that it must be exact and sourced from the search tool, which reduces guess-and-check calls.

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 chart row') plus the exact key used ('by its exact chart_uid'), and explicitly names the sibling datasets_steam_charts_search as the different entry point. An agent can immediately tell this apart from the search tool.

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?

The final sentence routes the agent to datasets_steam_charts_search to obtain a chart record, which implies this tool is the second step after a search. It does not explicitly state the inverse (do not call this tool with a made-up id) beyond the 404 note, so it stops short of full when/when-not guidance.

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

All Crawlora MCP tools Inspect

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

Need Help?