Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

preview_generator

Preview a single ASCII art frame from a generator to test settings like color, density, and seed before applying to the project.

Instructions

Preview a single frame from a generator without applying to the project.

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": {
      "generator": "<generator>"
    },
    "name": "preview_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
generatorYesGenerator type
colorNoPrimary color#00FF00
densityNoElement density
seedNoRandom seed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It states that the tool does not apply the generator to the project, which is a key behavioral trait. However, it does not describe what the preview output is (e.g., a data URL, an image), whether the generator state is altered, or any permission requirements.

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?

The description is a single sentence that clearly states the purpose and key differentiator. It is front-loaded and contains no unnecessary words.

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 no output schema, the description should clarify what the tool returns (e.g., a preview data URL). It also does not mention whether it modifies state or requires any permissions. The description is too minimal for a tool with 4 parameters and no annotations.

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?

All 4 parameters have descriptions in the schema (100% coverage). The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Preview') and resource ('single frame from a generator'), and explicitly notes it does not apply to the project. This clearly distinguishes it from the sibling `run_generator` tool.

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 for testing or viewing a generator output before committing, but it does not explicitly state when to use it versus alternatives like `run_generator` or `get_canvas_preview`. 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.

Deploy Server

Other Tools