Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_steam_charts_item

Retrieve one stored Steam chart snapshot row by chart_uid from search results, giving you the exact stored chart record when you need a single row's details.

Instructions

Get one stored Steam chart row. Retrieves one Steam chart snapshot row by chart_uid from datasets_steam_charts_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": {
      "chart_uid": "<chart_uid>"
    },
    "name": "datasets_steam_charts_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_uidYesExact chart_uid from a search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/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. 'Get'/'Retrieves' and 'stored ... snapshot row' convey read-only access to persisted snapshot data, which is useful context beyond the schema. It does not disclose not-found behavior, error modes, or whether the row can change between calls, leaving meaningful gaps for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no extraneous content. The two sentences largely restate the same fact ('Get one stored Steam chart row' vs 'Retrieves one Steam chart snapshot row'), which is minor redundancy rather than a structural problem.

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 one-parameter lookup with no output schema, the definition covers what is fetched, the required key, and where the key comes from. The remaining gap, behavior on a missing or stale uid, is small relative to the tool's simplicity.

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?

There is a single parameter with 100% schema description coverage, and the schema already states 'Exact chart_uid from a search result'. The description's 'from `datasets_steam_charts_search`' only adds the originating tool name, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get one stored Steam chart row') and adds the retrieval key ('by `chart_uid`'), which distinguishes it from the sibling search/facets tools. It anchors the tool as the single-row counterpart to `datasets_steam_charts_search`, so an agent can tell what it does without opening 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'from a search result' and the parameter note 'Exact chart_uid from a search result' imply the intended workflow: search first, then fetch the row by uid. However, there is no explicit when-to-use/when-not statement, no mention of what happens with an invalid uid, and no stated alternative such as re-running the search.

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