Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_package

Fetch store details for a purchasable bundle—name, included apps, price, platforms, and release date—using its package ID, with optional region and language.

Instructions

Get Steam store details for a package. Returns 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.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
packageidYesNumeric Steam package id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly signals a read-style lookup ('Get'/'Returns') and discloses the shape of the result (name, contained apps, price, platforms, release date), which is genuinely useful given there is no output schema. It stops short of stating error behavior, rate limits, or auth needs.

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?

Three front-loaded sentences that lead with the purpose and then detail the return content. Minor redundancy between 'Get Steam store details for a package' and 'Returns details for a Steam package' keeps it just short of a 5.

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 three-parameter read tool with no annotations and no output schema, the description covers the essential purpose, return fields, and the role of the country code. It is nearly complete, with only edge-case/error behavior unaddressed.

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 coverage is 100%, so the schema already documents all three parameters. The description's note that 'cc selects the store region and price currency' largely restates the schema's 'selects currency,' adding only marginal regional framing, so the 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 ('Get') and resource ('Steam store details for a package'), and explicitly defines the resource as 'a purchasable bundle,' which distinguishes it from sibling tools like steam_app and steam_search. It also enumerates the returned fields, so an agent knows exactly what this tool yields.

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?

Usage is only implied: fetch a package by id when you want bundled store details. There is no explicit when-to-use/when-not guidance and no named alternatives (e.g., steam_app for individual titles), leaving the agent to infer selection from the resource definition alone.

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