Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_latest

Fetch PlayStation Store new-release shelves with titles, prices, and a combined item list. Select region and language via cc and l.

Instructions

Get PlayStation Store latest-release shelves. Returns the PlayStation Store latest-releases landing page as a list of merchandising shelves (sections), each with its titles and per-item price, plus a flattened, de-duplicated item list across all shelves. 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. Credential-free public PlayStation Store data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations are not provided, so the description must carry behavioral disclosure. It mentions that cc selects region and currency, l selects language, and it's credential-free public data. However, it doesn't disclose potential rate limits, pagination, or how shelves are organized (e.g., whether they are sorted by date). The credential-free note is useful, but more could be said about response behavior.

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?

The description is two sentences with no redundancy. It front-loads the core purpose (get latest shelves) and then details the output structure and parameters. Each sentence earns its place, though it could be slightly more concise in the flattened list detail.

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?

Given the tool has no required parameters, no output schema, and no annotations, the description covers the essential inputs (cc and l) and output structure (shelves, prices, flattened list). It's complete enough for an agent to call correctly, though it omits details like default region/language behavior or error cases, which are minor for a read-only tool.

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% for both parameters, so the schema already explains l and cc simply. The description adds value by specifying that cc selects currency and l uses primary language, which is not in the schema. This compensates slightly but doesn't go beyond what a savvy agent could infer.

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?

The description clearly states it fetches PlayStation Store latest-release shelves, returning merchandising shelves with titles and prices, and a flattened de-duplicated item list. It is specific about the resource and output, but it doesn't explicitly differentiate from siblings like playstation_browse or playstation_category, though the focus on 'latest releases' distinguishes it sufficiently for an agent.

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?

The description implies this tool is for getting the latest-releases landing page when needing shelves and flattened items, but it doesn't explicitly state when to use it over other PlayStation tools like playstation_browse or playstation_search. No exclusions or alternatives are mentioned, leaving the agent to infer from the 'latest-release' specificity.

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