Skip to main content
Glama
CameronFoxly

ASCII Motion MCP

by CameronFoxly

apply_effect

Apply visual effects to an ASCII art frame or selection. Adjust colors, characters, brightness, contrast, hue, saturation, or apply invert, grayscale, or scatter distortions.

Instructions

Apply a visual effect to the current frame or selection. Effects modify colors and/or characters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectYesType of effect to apply
brightnessNoBrightness adjustment (-100 to 100)
contrastNoContrast adjustment (-100 to 100)
hueNoHue shift in degrees (-180 to 180)
saturationNoSaturation adjustment (-100 to 100)
lightnessNoLightness adjustment (-100 to 100)
colorMapNoMap of old colors to new colors (e.g., {"#FF0000": "#00FF00"})
characterMapNoMap of old characters to new (e.g., {"@": "#", "*": "+"})
targetPaletteNoTarget color palette for automatic remapping
scatterAmountNoMaximum pixel displacement for scatter effect
frameIndexNoFrame to apply effect to (defaults to current)
applyToSelectionNoOnly apply effect within current selection
affectForegroundNoApply color effects to foreground colors
affectBackgroundNoApply color effects to background colors
Behavior2/5

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

No annotations exist, so the description must fully convey behavior. It only states that effects modify colors/characters, without disclosing side effects (e.g., destructive overwrite), reversibility, or interaction with existing effect blocks. This is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, front-loaded sentence with clear purpose. No extraneous information.

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 complexity (14 parameters, no output schema), the description is too brief. It lacks information about return values, error handling, and behavior when multiple parameters conflict. Incomplete for effective use.

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 coverage is 100%, so baseline score is 3. The description adds no extra meaning beyond the schema parameter descriptions; it only restates that effects modify colors/characters.

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 the verb 'apply' and the resource 'visual effect', specifying it works on the current frame or selection and modifies colors/characters. However, it does not differentiate from sibling tools like add_effect_block or add_effect_keyframe.

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?

No guidance on when to use this tool versus alternatives like add_effect_block (which likely supports animation) or other editing tools. No prerequisites or when-not-to use information provided.

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