Skip to main content
Glama
Sign In

Playgama MCP - Publish & Manage HTML5 Games

by com.playgama.developer
OverviewDiscussionsAdmin

Replace the in-app catalog

replace_in_app_products
Destructive

Replace the whole in-app catalog with products — not a patch: a product you leave out is deleted, and an empty list clears the catalog. Ask the developer before removing products. Read list_in_app_products first and pass its checksum as expectedChecksum; if the catalog changed meanwhile, the call is refused. While in-game purchases are off, a call that leaves them off is refused (IN_GAME_PURCHASES_OFF): turn them on with hasInGamePurchases: true to change the catalog.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "applicationId": "<applicationId>",
      "products": "<products>",
      "expectedChecksum": "<expectedChecksum>"
    },
    "name": "replace_in_app_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesThe complete catalog after your change
applicationIdYesGame id from list_applications
expectedChecksumYesThe `checksum` list_in_app_products answered — the state this call means to replace
hasInGamePurchasesNoDefaults to whether `products` is non-empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / applicationId / description
      Previous value: -"Application (game) id, as returned by list_applications"New value: +"Game id from list_applications"
  2. Changed3 schema fields changed
    • addedInput schema / properties / products / items / properties / description / description
      Added value: +"Product description"
    • addedInput schema / properties / products / items / properties / title / description
      Added value: +"Display title of the product"
    • addedInput schema / properties / products / items / properties / type / description
      Added value: +"`consumable` can be bought again and again (coins, lives); `non_consumable` is bought once and kept"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the crucial semantics behind that: omitted products are deleted and an empty list wipes the catalog. It further discloses optimistic-concurrency refusal on checksum mismatch and the in-game-purchases precondition with its error code.

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?

Front-loaded with the destructive whole-replace semantics, then the prerequisite workflow, then the precondition. Dense but each clause carries information; slightly heavy sentence nesting around the in-game purchases rule costs it a point.

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

Completeness5/5

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

For a destructive, non-idempotent, four-parameter mutation with no output schema, the definition covers scope, data loss, ordering prerequisites, concurrency handling, and the blocking precondition. Nothing an agent needs to call it safely is missing.

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%, so every parameter is already documented, including the checksum's source and the `hasInGamePurchases` default. The description mainly reinforces the concurrency contract rather than adding new per-parameter meaning beyond what the schema says.

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?

States a specific verb and resource ('Replace the whole in-app catalog') and immediately disambiguates it from a patch operation. Naming `list_in_app_products` as the read-side sibling makes the replace-vs-list distinction explicit without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite ordering: read `list_in_app_products` first and pass its `checksum` as `expectedChecksum`. It also names the human-confirmation step before removing products and the exact remedy for the IN_GAME_PURCHASES_OFF refusal, so the agent knows both when to use it and how to recover from the known failure mode.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Playgama MCP - Publish & Manage HTML5 Games toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources