Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_product

Fetch PlayStation Store details for one product or edition, including title, publisher, release date, platforms, genres, languages, rating, price, and media. Set region and language with cc/l codes.

Instructions

Get PlayStation Store details for a single product. Returns store metadata for a single PlayStation product/edition: title, np title id, parent concept id, product type and store classification, edition name, publisher, release date, platforms, genres, spoken/screen languages, content rating, aggregate star rating, purchase price, and media. cc selects the store region (and price currency); l accepts a language code or locale such as en or en-US, with the locale's primary language used for text.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
idYesPlayStation product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. "Get" implies a read-only retrieval, and the description lists the returned fields and explains the region/currency effect of cc, but it omits permissions, error behavior, and any rate-limit or edition-vs-concept relationship details.

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?

Front-loads the purpose, then the return payload, then parameter effects. The return-field enumeration is long but each item is informative for a tool lacking an output schema, and there is no filler.

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?

No output schema exists, so the description justifiably enumerates return fields, making it fairly self-sufficient. It is slightly incomplete on the expected id format and any failure/fallback behavior, but covers the essential call semantics.

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% (baseline 3), and the description adds real value beyond the terse schema strings: it clarifies that cc selects the store region and therefore the price currency, and that l accepts a language code or locale with the locale's primary language used for text. This is meaningful semantics not present in the schema.

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 ("PlayStation Store details for a single product") and explicitly scopes to a single product/edition. This distinguishes it from list/search siblings like playstation_search, playstation_browse, or playstation_category without opening any 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?

The phrase "for a single product" conveys that it is for detail lookup by id, giving clear usage context. However, it never names alternatives (e.g., playstation_concept for concept/edition grouping or playstation_search to find the id), so the when-not-to-use case is left to inference.

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