Skip to main content
Glama

Asset export planner

plan_asset_exports
Read-only

Builds an export plan. Pass assets as lines like search-icon | 24x24 | icon | web, ios, android or as a JSON array of {name, width, height, kind, platforms}. Kinds: icon, logo, illustration, photo, ui, background, favicon, app-icon, og-image, sprite. For each asset returns the recommended format (SVG for vector kinds, AVIF or WebP with JPEG fallback for photos, PNG for flat UI), web 1x to 3x sizes, iOS @2x and @3x, Android mdpi to xxxhdpi sizes (1, 1.5, 2, 3, 4 times), favicon and PWA sizes, adaptive icon geometry, the 1200x630 social card, and warnings for fractional or odd sizes. Rules of thumb that change over time; confirm against current platform docs. Computes sizes only and produces no files.

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": {
      "assets": "<assets>"
    },
    "name": "plan_asset_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYesLines like `name | 24x24 | icon | web, ios`, or a JSON array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond that: it computes sizes only, produces no files, returns warnings for odd sizes, and notes that the rules of thumb can change and should be confirmed against current platform docs.

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 front-loaded with the core purpose, then efficiently covers input formats, supported kinds, computed outputs, and scope limitations. It is dense but well organized, and every major sentence contributes useful information.

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

Completeness4/5

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

With no output schema, the description appropriately carries the burden of explaining what is returned: recommended formats, web, iOS, and Android sizes, favicon and PWA sizes, adaptive icon geometry, the social card, and warnings. It is nearly complete for a one-parameter planning tool, though it could say more about malformed input handling.

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% and the single parameter is documented, but the description adds substantial meaning beyond the schema by showing concrete input syntax, explaining the accepted asset kinds, and describing platform-specific size outputs. It does not fully document edge cases such as delimiter escaping, but it is clearly more helpful than the schema alone.

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 description states a specific verb and resource: 'Builds an export plan' for assets, and clarifies that it computes sizes only and produces no files. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as plan_responsive_images or logo_size_rules.

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?

The description implies the tool is used when an agent needs export dimensions and formats for assets across web, iOS, Android, favicon, and social contexts. However, it does not state when to use this instead of alternative planning tools, nor does it include explicit exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources