Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_replace_char

Replace one character with another across an entire ASCII frame or selection, enabling bulk character substitution in animated ASCII art.

Instructions

Replace one character with another across the entire frame or selection.

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": {
      "oldChar": "<oldChar>",
      "newChar": "<newChar>"
    },
    "name": "batch_replace_char"
  }
}

Input Schema

NameRequiredDescriptionDefault
oldCharYesCharacter to replace
newCharYesNew character
frameIndexNoFrame to modify (defaults to current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behaviors. It states 'across the entire frame or selection' but does not clarify how selection is determined, whether it affects all layers, or if changes are reversible. This is insufficient for full transparency.

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, well-structured sentence that conveys the core functionality without unnecessary words. Every part earns its place.

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

Completeness3/5

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

For a simple 3-parameter tool with no output schema, the description is minimally adequate. However, it lacks details about selection behavior, return values, and error conditions, leaving gaps for an AI agent to interpret correctly.

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%, meeting a baseline of 3. The description adds context about scope ('frame or selection') which relates to the optional frameIndex parameter, but does not significantly enhance understanding of oldChar and newChar beyond the schema definitions.

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 ('Replace') and resource ('character'), and clearly defines the scope ('across the entire frame or selection'). This distinguishes it from siblings like batch_recolor (color replacement) and set_cell (single cell modification).

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 usage for character replacement but provides no explicit guidance on when not to use it or alternatives. It does suggest a context (frame or selection) but lacks exclusions or comparative advice.

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