Skip to main content
Glama
CameronFoxly

ASCII Motion MCP

by CameronFoxly

run_generator

Generate procedural animation frames using generators like digital rain, radio waves, particle physics, and more. Customize colors, speed, density, and other parameters for unique ASCII animations.

Instructions

Generate procedural animation frames. Creates new frames with animated patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
generatorYesGenerator type
frameCountNoNumber of frames to generate
frameDurationNoDuration of each frame in ms
colorNoPrimary color (hex)#00FF00
secondaryColorNoSecondary color for gradients
backgroundColorNoBackground colortransparent
characterSetNoCustom characters to use (overrides default)
densityNoDensity of elements (0-1)
speedNoAnimation speed multiplier
trailLengthNoLength of trails
waveSpeedNoWave expansion speed
waveCountNoNumber of simultaneous waves
centerXNoWave center X (defaults to canvas center)
centerYNoWave center Y (defaults to canvas center)
noiseScaleNoNoise scale (smaller = more detailed)
noiseSpeedNoHow fast noise evolves
particleCountNoNumber of particles
gravityNoGravity effect (-1 to 1)
replaceFramesNoReplace existing frames (otherwise append)
seedNoRandom seed for reproducibility
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states that frames are generated and created, but does not mention side effects like frame replacement (controlled by 'replaceFrames' parameter), potential project modification, or required canvas state. This is insufficient given the tool's complexity.

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 concise with only two sentences, but it may be overly terse. It front-loads the basic purpose, but a bit more detail would improve clarity without harming conciseness.

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

Completeness2/5

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

Given the tool's 20 parameters and no output schema, the description is incomplete. It does not explain what the tool returns, how it affects the project, or provide usage context. The complexity demands more information than provided.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema, failing to explain how parameters interact or which are relevant for specific generators. It does not compensate for the lack of guidance on parameter usage.

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 clearly states 'Generate procedural animation frames' and 'Creates new frames with animated patterns', which specifies the verb and resource. However, it does not explicitly differentiate from sibling tools like 'preview_generator' or 'add_frame', leaving some ambiguity about when to use this specific tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'preview_generator' for previewing or 'add_frame' for adding empty frames. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CameronFoxly/ascii-motion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server