Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_region_to_frame

Copy a rectangular region of ASCII art from one animation frame to another, specifying source and target frames and region boundaries.

Instructions

Copy a region of cells from one frame to another

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": {
      "sourceFrame": "<sourceFrame>",
      "targetFrame": "<targetFrame>",
      "sourceRegion": "<sourceRegion>"
    },
    "name": "copy_region_to_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceFrameYesSource frame index
targetFrameYesTarget frame index
sourceRegionYesRegion to copy from source
targetPositionNoPosition to paste at in target (defaults to same position)
overwriteNoIf true, overwrite existing cells in target

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose default overwrite behavior (though schema has default true), side effects, or what happens if target region has existing content.

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 a single sentence with no unnecessary words. It is appropriately front-loaded but may be too brief, sacrificing detail.

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 complexity (5 params, nested objects, no output schema), the description lacks mention of defaults, return values, or limitations. It is insufficient for a complete understanding.

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 schema already documents all parameters. The description adds no additional meaning beyond restating the tool's purpose.

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 action: copying a region of cells between frames. It distinguishes from siblings like fill_region or flip_region. However, it could be more specific about 'cells' meaning cell contents.

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 fill_region or shift_frame_content. The description simply states what it does without context or exclusions.

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