Skip to main content
Glama

List assets

list_assets

Lists image and sound files in RPG Maker MV asset folders, showing sizes, PNG dimensions, and optional usedBy/unused warnings to verify references before deleting or editing assets.

Instructions

List the image and sound files in the project's asset folders (img/* and audio/*, 18 folders; all of them or one folder). Each file shows its name (without extension), ext, size in bytes and, for images, the pixel size read from the PNG header, plus warnings (a header that does not match the extension, or a sheet size that does not fit the folder). Only the first 64 bytes of each file are read, so a sound's type is judged from its header alone, not the codec or the whole file. Sub-directories and files with other extensions (.rpgmvp, .txt, ...) are skipped. With includeUsage (default true), files in the folders the reference scan covers (all except img/system and img/animations) get usedBy (at most 3 places, e.g. 'Actor 1', 'Map003 event 5') and unused (true when nothing in the database, maps, common events or troops references the name). Names are matched case-sensitively, so a reference that differs only in letter case shows the file as unused: run audit_assets to find case mismatches and missing files. A plugin or script that loads a file by name is not seen, so check before deleting. Files with names outside the import rule (dots, non-ASCII) are listed too, but preview_asset cannot open them. Interlaced PNGs are flagged in warnings. A folder that cannot be read gets an error on its entry instead of failing the listing. Files are sorted by name; each folder shows at most limit files and truncated counts the rest.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum files listed per folder
folderNoOnly this folder, e.g. img/characters; omit for all folders
includeUsageNoAdd usedBy/unused (scans the project's data files)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.9/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 discloses many behavioral traits: only first 64 bytes read, sound type judged from header alone, sub-directories and other extensions skipped, case-sensitive name matching, usedBy/unused semantics, error handling for unreadable folders, sorting, and truncation behavior.

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?

The description is a single dense paragraph with no wasted sentences, but its length and compactness make it harder to scan than a structured list. It is front-loaded with the purpose, but could benefit from better organization.

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?

There is no output schema or annotations, so the description must cover return format and behavior. It does: fields per file, warnings, error entries, usedBy/unused details, truncation, and sorting. Nothing essential for correct invocation is missing.

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

Parameters5/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 substantial meaning: includeUsage default true, which folders the reference scan covers (all except img/system and img/animations), what usedBy and unused mean, and how limit and truncated work per folder.

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?

The description states a specific verb and resource: 'List the image and sound files in the project's asset folders', and scopes it to img/* and audio/*. It distinguishes from siblings by naming audit_assets and preview_asset in context.

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?

It explicitly says to run audit_assets for case mismatches and missing files, and to check for plugin/script loads before deleting. It also clarifies that files outside the import rule are listed but preview_asset cannot open them, giving clear when-to-use and when-not-to-use guidance.

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