2d-assets-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_mock_assetA | Generates a single advanced custom mock 2D PNG asset (supports gradients, patterns, text rotation, transparency, and auto-scaling) for game prototypes. Embeds JSON metadata into the PNG (dimensions, color, shape, description) readable by read_image_metadata. |
| generate_mock_asset_batchA | Generates multiple mock 2D PNG assets at once. Can create individual files, a spritesheet, Each PNG has embedded JSON metadata readable by read_image_metadata. |
| read_image_metadataA | Reads the embedded JSON metadata from a PNG file generated by this MCP server. Returns the metadata object with dimensions, color, shape, description, etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: generate single asset, generate multiple assets, and read metadata. The single vs. batch distinction is clear, and read_image_metadata is entirely separate.
All tool names follow a consistent verb_noun pattern in snake_case: generate_mock_asset, generate_mock_asset_batch, read_image_metadata. The convention is uniform.
Three tools is well-scoped for a niche server focused on generating and inspecting mock 2D assets. Each tool serves a necessary function without redundancy.
The tool surface covers the full workflow: generating a single asset, generating batches (including spritesheets), and reading embedded metadata. No obvious gaps for the stated domain.