Skip to main content
Glama
Sign In
mcp-ps-store

mcp-ps-store

by murzin-ml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Purchased PSN library

psn_owned_games
Read-only

Check a PlayStation account's owned and claimed games, including playtime, to avoid recommending games already purchased and highlight unplayed titles.

Instructions

Games the account has bought or claimed (including PS Plus monthly claims), with hours played where known. Check this before recommending anything so you do not suggest a game the user already owns, and to surface unplayed purchases.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "psn_owned_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNo
platformNoall
unplayed_onlyNoKeep only games with no recorded playtime.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint=true, the safety profile is already established by annotations. The description adds useful behavioral context beyond that: the inventory includes PS Plus claims, playtime data is only present 'where known', and the tool is meant to surface unplayed purchases. No contradiction with the annotations is present.

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 two tight sentences with no filler. The first sentence front-loads the data scope, and the second sentence explains when and why to use the tool, earning every word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core use case well and an output schema exists, so return-value details are not needed. However, with five parameters and only 20% schema coverage, the descriptions do not fully explain how to leverage search, platform filtering, or pagination. It also does not contrast with psn_library, which may be a close sibling, leaving some contextual ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description needed to compensate for limit, offset, search, and platform, but it does not explain any of those. Only 'unplayed purchases' loosely maps to the unplayed_only parameter. The parameter names are somewhat self-explanatory, which keeps this above a 1.

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 specifies the resource: games the account has bought or claimed, including PS Plus monthly claims, with hours played where known. It also states the practical purpose: avoid recommending owned games and surface unplayed purchases. It stops short of explicitly distinguishing itself from the sibling psn_library, so it is not a full 5.

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 an explicit trigger: 'Check this before recommending anything' and explains why, preventing duplicate game suggestions and highlighting unplayed purchases. It does not name sibling alternatives or state when not to use it, but the guidance is clear enough for an agent to know when to call it.

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