Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_layer

Remove a specific layer from your ASCII art animation by providing its layer ID. Ensures at least one layer remains.

Instructions

Remove a layer by ID. Cannot remove the last remaining layer.

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": {
      "layerId": "<layerId>"
    },
    "name": "remove_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerIdYesID of the layer to remove

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 the burden of behavioral disclosure. It states a key behavioral trait: the tool cannot remove the last remaining layer, which prevents errors. However, it does not mention reversibility or side effects on child content, but the core destructive nature is clear.

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 concise sentences with no wasted words. The important constraint is front-loaded, making the description efficient and easy to parse.

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?

Given a single parameter and no output schema, the description covers the essential purpose and a critical constraint. It is fairly complete for a simple deletion tool, though it omits details about potential side effects on associated content.

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?

The input schema has 100% coverage, with layerId described as 'ID of the layer to remove'. The description adds minimal value by just restating 'by ID', but it reinforces the context. Baseline 3 is appropriate given high schema coverage.

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 ('remove a layer by ID') and a critical constraint ('Cannot remove the last remaining layer'). This distinguishes it from sibling tools like add_layer, duplicate_layer, etc., which have different purposes.

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 when to use (when you need to delete a layer) and hints at a constraint (not if it's the last layer), but it does not explicitly mention alternatives or when not to use it. For a simple removal tool, this is adequate but not fully comprehensive.

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