Skip to main content
Glama
Sign In
ASCII Motion MCP

ASCII Motion MCP

by CameronFoxly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_content_frame

Removes a specified content frame from a layer, enabling precise frame deletion in ASCII animations.

Instructions

Remove a content frame from a 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>",
      "contentFrameId": "<contentFrameId>"
    },
    "name": "remove_content_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerIdYesLayer ID
contentFrameIdYesContent frame ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.4

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It only states the action, omitting details like whether the removal is permanent, what happens if the frame doesn't exist, or any side effects on the layer.

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, concise sentence that is front-loaded with the verb and resource. While efficient, it lacks additional valuable context that could improve usability.

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 tool has two required parameters and no output schema or annotations, the description is incomplete. It fails to explain return values, error conditions, or whether the operation is reversible, which is necessary for agents to use it safely.

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%, with basic parameter descriptions ('Layer ID', 'Content frame ID to remove'). The tool description adds no additional meaning or constraints beyond what the schema already provides.

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') and the resource ('content frame from a layer'), distinguishing it from sibling tools like 'add_content_frame' (opposite) and other removal tools such as 'remove_effect_block' or 'remove_layer'.

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 is provided on when to use this tool versus alternatives, such as when a content frame should be removed or if there are prerequisites (e.g., the layer must exist). This leaves the agent without context for appropriate invocation.

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