Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_deals

Fetch PlayStation Store deals shelves by country and language, returning each section's titles, prices, and a deduplicated item list from public credential-free store data.

Instructions

Get PlayStation Store deals shelves. Returns the PlayStation Store deals 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

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It states the operation is a read-style 'Get' over 'credential-free public PlayStation Store data' and describes the returned structure, including the flattened, de-duplicated item list. It does not mention pagination, default locale/region behavior, or rate limits, but for a simple public fetch the transparency is solid.

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?

The description is three sentences with no filler. It front-loads the core purpose, then explains the return structure, then covers parameters and access requirements. Every sentence earns its place.

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?

There is no output schema, so the description correctly explains the return format and parameter semantics. It is complete enough for an agent to call the tool correctly, though it could briefly mention what happens when cc or l are omitted. Overall, it is well-rounded for a low-complexity, two-optional-parameter tool.

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%, so the baseline is 3. The description adds meaningful extra semantics beyond the schema: cc selects both store region and price currency, and l accepts either a language code or a locale like en-US, with the primary language used. These details help an agent choose correct values.

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?

The description names a specific verb and resource: 'Get PlayStation Store deals shelves.' It also details the output shape (merchandising shelves, titles, per-item price, flattened de-duplicated list), which clearly distinguishes it from sibling tools like playstation_browse, playstation_search, or playstation_category. An agent can immediately know what this tool is for.

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 description gives clear context for when this tool is appropriate: retrieving PlayStation Store deals shelves. It explains the two optional parameters and notes the data is credential-free, giving an agent enough to decide to use it. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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