Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_water_reflection

Creates a deterministic animated water reflection below a given waterline for ocean, beach, or wave scenes, using a seed for consistent output and adjustable frames, opacity, and amplitude.

Instructions

Generate a deterministic animated reflection below a waterline for oceans, beaches, and wave scenes.

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": {
      "input_filename": "<input_filename>",
      "output_filename": "<output_filename>",
      "waterline": "<waterline>"
    },
    "name": "generate_water_reflection"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNo
formatNo
framesNo
opacityNo
delay_msNo
amplitudeNo
waterlineYes
input_filenameYes
output_filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the output is deterministic and animated, but it says nothing about file overwriting, input/output dependencies, resource usage, or failure modes—significant gaps for a tool that generates an output file.

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 single sentence has no fluff and is front-loaded with the core purpose, but it is drastically undersized for a tool with 9 parameters, no annotations, and no output schema. Brevity here is under-specification rather than effective conciseness.

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

Completeness1/5

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

Given the complexity signal of 9 parameters, 0% schema coverage, no annotations, and no output schema, one sentence is far from complete. An agent cannot determine how parameters interact, what file formats are expected, or what the generated output will look like.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 9 parameters, so the description must compensate, but it does not explain any parameter meanings. It only references 'waterline' as a conceptual location, leaving seed, amplitude, delay_ms, format, frames, opacity, input_filename, and output_filename entirely undocumented.

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 ('Generate') and a concrete resource ('deterministic animated reflection below a waterline'), and scopes it to oceans, beaches, and wave scenes. This clearly distinguishes it from sibling tools like generate_water_caustics or generate_beach_scene, which target different effects.

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 phrase 'for oceans, beaches, and wave scenes' gives an implied usage context, but it does not explicitly say when to choose this tool over related alternatives such as generate_water_caustics or generate_scene_effect_stack. There are no when-not-to-use conditions or alternative routing 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