Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_frame_and_modify

Duplicate a frame and apply cell modifications in one operation to build animation sequences efficiently.

Instructions

Duplicate a frame and apply modifications in a single operation. Efficient for creating animation sequences.

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": {
      "sourceIndex": "<sourceIndex>",
      "modifications": "<modifications>"
    },
    "name": "copy_frame_and_modify"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceIndexYesIndex of frame to copy
modificationsYesCell modifications to apply to the new frame
insertAtIndexNoWhere to insert the new frame (defaults to after source)
nameNoName for the new frame
durationNoDuration for the new frame

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses that modifications apply to the new frame and the operation is a single step. However, it does not mention behavioral traits like whether the original frame remains unchanged, error conditions, or required permissions.

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 two sentences long. The first sentence states the core action, the second adds a use case. Both are necessary and front-loaded; no wasted words.

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?

The tool has 5 parameters and no output schema. The description covers the high-level purpose but does not explain the return value (e.g., index of new frame) or side effects. For a mutation tool without annotations, more detail on behavior would improve completeness.

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 description adds minimal additional meaning beyond the schema. It mentions 'Cell modifications to apply to the new frame' but does not elaborate on parameter details beyond what is already in the schema.

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 clearly states the action ('Duplicate a frame and apply modifications') and the resource ('a frame'). It distinguishes from sibling 'duplicate_frame' by combining modification in one step, and provides a use case ('efficient for creating animation sequences').

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

Usage Guidelines4/5

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

The description implies when to use this tool (for creating animation sequences by duplicating and modifying in one step). It does not explicitly state when not to use or mention alternatives, but the context is clear.

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