Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_layer

Adds a new layer to the project, converting from legacy frame mode to layer mode if required.

Instructions

Add a new layer to the project. If project is in legacy frame mode, this switches it to layer mode.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLayer name (auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses an important behavioral trait: if the project is in legacy frame mode, it switches to layer mode. This goes beyond the basic purpose, though it omits other potential effects (e.g., undoability, default layer properties).

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?

Two sentences, front-loaded with the primary action. Every word earns its place; no fluff.

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

Completeness4/5

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

Despite no output schema, the description covers purpose and a key behavioral detail. It lacks return value information but is largely sufficient for a simple one-parameter tool with high schema coverage.

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 the schema already describes the single optional parameter. The description adds no extra meaning beyond what is in the schema. 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 clearly states the action ('Add a new layer') and the resource ('to the project'). It distinguishes from siblings like duplicate_layer by specifying it creates a new blank layer. The mention of switching from legacy frame mode to layer mode adds specificity.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., duplicate_layer). The note about legacy frame mode provides a conditional usage scenario but does not cover typical use cases 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