Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_category

Browse a PlayStation Store category grid by UUID to retrieve paginated items with prices, platforms, media, and filter facet counts; set region and language as needed.

Instructions

Browse a PlayStation Store category grid. Returns a page of a specific PlayStation Store category grid (by category UUID) with per-item price, platforms, and media, plus the available filter facets with value counts. Pass page to advance; next_page is set when more results exist. 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)
idYesCategory UUID
pageNo1-based page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/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. It does disclose the return contents (per-item price, platforms, media plus filter facets with value counts) and pagination behavior ('next_page is set when more results exist'), which is useful. It says nothing about auth, rate limits, or explicit read-only status, so it stops short of full behavioral 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?

Three sentences, purpose front-loaded, with pagination guidance following. Slightly redundant in restating 'PlayStation Store category grid' twice across the first two sentences, but overall tight and useful.

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 browse/list tool with no output schema and no annotations, the description covers return payload, pagination, and region/language behavior, which is what an agent needs to call it correctly. Missing only safety/auth context, which is minor here.

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 value beyond it: it clarifies 'l' accepts a locale such as en or en-US and that the locale's primary language is used for text, and that 'cc' selects region and currency. That exceeds the terse schema field descriptions.

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?

Specific verb+resource: 'Browse a PlayStation Store category grid' keyed by a category UUID, and it states the returned payload (prices, platforms, media, filter facets). This distinguishes it from product/search siblings, though no sibling is named explicitly.

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?

Implicitly conveys that a category UUID is the entry point and that 'page' advances results, but gives no when-to-use/when-not guidance or alternatives (e.g., vs playstation_browse or playstation_search). Usage must be inferred.

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