Skip to main content
Glama
Xerolo44

RPG Maker MV MCP Server

by Xerolo44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview asset

preview_asset

Displays a PNG asset from an RPG Maker MV img folder as an image with its pixel dimensions and file size, including character/face sheet layout, scaled to a maximum edge size.

Instructions

Show a PNG from an img/* folder as an image so you can see it, with its pixel size, file size and, for img/characters and img/faces, the sheet layout implied by the name and size. name is the file name without .png and must match an existing file exactly (see list_assets). The image is scaled down (nearest neighbour, aspect kept) to at most maxSize pixels on its longer edge; smaller images are shown as they are. Files over 32 MiB or 16 million pixels, interlaced PNGs and files that are not valid PNGs are refused. Only names that pass the asset name rule (1-64 characters from A-Z a-z 0-9 space _ ! $ ( ) -) can be opened, even though list_assets may show files with other names. Audio cannot be previewed.

Input Schema

NameRequiredDescriptionDefault
nameYesFile name without extension, e.g. Actor1
folderYesImage folder, e.g. img/characters
maxSizeNoLongest edge of the returned image in pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses downscaling behavior (nearest neighbour, aspect preserved, only larger images scaled), the maxSize semantics on the longer edge, and a detailed refusal list (32 MiB, 16M pixels, interlaced, invalid PNG, names failing the character rule). It effectively defines the tool's success and failure envelope without needing annotations.

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?

Purpose is front-loaded in the first clause, followed by output, then scaling and refusal constraints — a sane order. It is a dense single block with run-on sentences that would read better split, but no sentence is filler.

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?

No output schema exists, yet the description explains what the agent receives (the rendered image, pixel dimensions, file size, and sheet layout for certain folders). Combined with the detailed constraints, an agent has everything needed to call it correctly or predict a rejection.

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 baseline is 3, but the description adds real semantics: 'name' is the file name without .png and must match an existing file exactly, and maxSize only downscales images whose longer edge exceeds it. The folder enum itself is not expanded beyond 'img/*', which keeps it from a 5.

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 ('Show a PNG from an img/* folder as an image') plus the extras returned (pixel size, file size, sheet layout for img/characters and img/faces). This clearly distinguishes it from siblings like list_assets (enumeration) and render_map_image (map rendering).

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?

Gives clear context for use and a negative case ('Audio cannot be previewed'), and routes the agent to list_assets to find valid names. It does not explicitly delimit itself against adjacent image siblings (get_tileset_image, render_map_image), so it stops short of full when/when-not/alternatives guidance.

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