Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_deals

Retrieve PlayStation Store deals shelves with per-title pricing, and get a flattened, de-duplicated item list across all sections. Set country and language to choose region, currency, and text.

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.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the burden well by disclosing the return shape: a list of merchandising shelves each with titles and per-item price, plus a flattened de-duplicated item list. It omits auth requirements, rate limits, and pagination, but the response-structure disclosure is genuinely useful context here.

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 ordered purpose, return shape, then parameters, all front-loaded with the core action. It is slightly dense but every sentence carries information; no obvious 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?

For a two-optional-parameter read tool with no output schema or annotations, the description covers what it returns and what the parameters mean, which is enough to call it correctly. Minor gaps remain around permissions and pagination but are not critical for invocation.

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, and the description adds real value: it explains that cc selects region and price currency, and that l accepts a language code or locale (en, en-US) with the primary language used for text. This clarifies behavior beyond the terse schema 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?

States a specific verb (Get) and resource (PlayStation Store deals landing page as merchandising shelves), and adds that prices are returned per item. It is clear what the tool does, though it does not name any sibling (e.g. playstation_browse, playstation_search, playstation_latest) to differentiate its scope from those.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance or alternative named. The phrase 'deals landing page' weakly implies the use case, but nothing tells the agent when to pick this over playstation_browse or playstation_category for the same content.

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