Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_playstation_games_item

Retrieve a PlayStation Store game by product ID from the playstation-games dataset, returning pricing, genres, ratings, release details, or a 404 if not found.

Instructions

Get a PlayStation game from dataset. Returns one PlayStation Store game from the playstation-games dataset by product id such as UP0001-PPSA01491_00-GAME000000000000: name, publisher, genres, platforms, region, release date, base and discounted price with currency and discount end time, star rating and rating count, content rating, and edition and add-on counts. An id that is not in the dataset returns 404.

Input Schema

NameRequiredDescriptionDefault
product_idYesPlayStation product id (e.g. UP0001-PPSA01491_00-GAME000000000000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.1/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 full burden. It discloses that the operation is a read keyed on product id and, importantly, that an id absent from the dataset yields a `404`, which is genuinely useful error semantics. It does not mention permissions, rate limits, or freshness, but the error contract plus the read nature is solid disclosure.

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 core action ("Get a PlayStation game from dataset") before enumerating fields, and each sentence carries information. The return-field list is dense but justified since no output schema exists to carry it.

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 a single required param, no annotations, and no output schema, the description covers purpose, the returned field set, and the miss case (404). That is nearly everything an agent needs; only id-discovery guidance toward the search sibling is missing.

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?

Only one parameter, and the schema already documents `product_id` at 100% coverage including the same example format. The description reinforces the id format and explains that it must exist in the dataset (404 otherwise), adding a small amount of meaning beyond the schema, so this sits slightly above the 3 baseline for a fully-covered single param.

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) plus resource (one PlayStation Store game from the `playstation-games` dataset) and pins the lookup key to a product id with a concrete example. This is clearly distinct from the sibling `datasets_playstation_games_search` and `..._facets` tools, which operate on collections rather than a single item.

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 implied: the tool is for retrieving one game by product id, and the 404 note tells the agent what happens on a miss. However, there is no explicit when-to-use/when-not guidance and no pointer to `datasets_playstation_games_search` for discovering valid ids, which is the most likely alternative an agent needs.

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