Rengi Forge

store_assets_stores

One key art and logo to the store images beyond Steam: itch.io cover 630x500, Google Play feature graphic 1024x500, Epic landscape 2560x1440 and portrait 1200x1600; gameplay screenshots fitted to Google Play 1920x1080 and App Store iPhone 6.9", 6.3" and iPad 13" sizes without stretching, no alpha where stores reject it. Price: $0.20 USDC via x402, charged only on success. Part of Store assets: Release art from one key art: every Steam store and library capsule at the exact required size with your logo placed per Steam's rules (never on the Library Hero), and full icon sets for iOS, Android adaptive icons, Google Play and the web..

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": {
      "keyArt": "<keyArt>"
    },
    "name": "store_assets_stores"
  }
}

Input Schema

Name	Required	Description
`logo`	No	Game logo with a transparent background.
`keyArt`	Yes	Main artwork without text, at least 1920 px wide.
`stores`	No
`screenshots`	No	Gameplay screenshots to fit to Google Play and App Store sizes.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real context: pricing ($0.20 USDC via x402, charged only on success), screenshots fitted 'without stretching', and alpha removed 'where stores reject it'. It stops short of naming auth requirements, failure modes, or output format, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a rambling run-on: the opening sentence is garbled, the pricing clause is spliced mid-paragraph, and the final 'Part of Store assets' sentence restates family scope while mentioning Steam work this tool does not perform. Useful facts are present but not front-loaded or cleanly separated.

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?

For a mutation/generation tool with no annotations and no output schema, the description covers inputs, target sizes, and cost reasonably well above the schema. It omits return values, delivery format, and failure handling, leaving gaps the agent must guess at.

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 75%, yet the description adds meaning beyond it by spelling out which stores are targeted and giving per-store target resolutions (itch 630x500, Google Play 1024x500, Epic 2560x1440/1200x1600, App Store 1920x1080). It also clarifies that screenshots apply only to Google Play and App Store, which the schema does not indicate.

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 tool generates non-Steam store images (itch.io cover, Google Play feature graphic, Epic landscape/portrait, App Store screenshots) from one key art and logo, with exact sizes enumerated. The phrase 'beyond Steam' cleanly differentiates it from the sibling store_assets_steam, though the trailing 'Part of Store assets' sentence confusingly re-describes the whole family including Steam capsules this tool does not produce.

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?

Usage is only implied: an agent infers this is for non-Steam store assets because the description says 'beyond Steam'. There is no explicit when-to-use vs store_assets_steam or store_assets_icons, and no exclusions other than the implicit store scoping.

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

All Rengi Forge tools Inspect

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

Need Help?