Crawlora MCP

steam_package

Read-only

Returns normalized details for a Steam package (a purchasable bundle): name, the apps it contains, price, platforms, and release date. cc selects the store region and price currency. Credential-free public Steam storefront JSON. packageid: Numeric Steam package id. Use steam_app to get Steam store details for an app.

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": {
      "packageid": "<packageid>"
    },
    "name": "steam_package"
  }
}

Input Schema

Name	Required	Description
`l`	No	Language code
`cc`	No	Store country code (ISO, selects currency)
`packageid`	Yes	Numeric Steam package id

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.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / cc / description
```
Added value: +"Store country code (ISO, selects currency)"
```
- addedInput schema / properties / l / description
```
Added value: +"Language code"
```
- addedInput schema / properties / packageid / description
```
Added value: +"Numeric Steam package id"
```
First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful context beyond that: 'Credential-free public Steam storefront JSON' tells the agent no auth is needed, and the field list sets return expectations. It could say more about error behavior for invalid package ids.

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?

Front-loaded with the purpose and returned fields, then supporting details. Mostly efficient, though the 'packageid: Numeric Steam package id' sentence duplicates the schema verbatim and could be dropped.

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?

With an output schema present, return values need not be re-explained, and the description covers resource identity, auth posture, and sibling routing. Complete enough for correct invocation; minor gaps are error/edge behavior.

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%, so the schema already documents all three params. The description restates packageid and adds region/currency semantics for cc, which is useful but largely redundant with the schema. Baseline 3 is appropriate.

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 (Returns) and resource (Steam package), clarifies what a package is ('a purchasable bundle'), and enumerates the returned fields. It also distinguishes itself from the sibling steam_app, so an agent can route without opening either schema.

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 names the alternative ('Use steam_app to get Steam store details for an app'), giving a clear routing rule. It does not cover the reverse case (when a package is preferred over an app) or other siblings like steam_search, but the key disambiguation is present.

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.