Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_set_layer_3d

Set a layer's 3D mode in an After Effects composition. Specify the composition and layer names, then set enabled to true for 3D or false for 2D.

Instructions

Enable or disable 3D mode on 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": {
      "comp_name": "<comp_name>",
      "layer_name": "<layer_name>",
      "enabled": "<enabled>"
    },
    "name": "ae_set_layer_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue = 3D on, false = 2D
comp_nameYesComposition name
layer_nameYesLayer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full burden of behavioral disclosure. It states the mutation but does not reveal side effects such as whether 3D transform values (z-position, orientation) are preserved when toggling back, whether locked layers are affected, or error behavior for missing layers. The potential data-visibility loss on toggle-off is undisclosed.

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?

A single front-loaded sentence with zero filler. Every word earns its place, and the description is appropriately sized for a simple toggle tool.

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?

For a simple three-parameter toggle with full schema coverage, the description is minimally viable. However, with no output schema, it does not indicate what a successful call returns or what happens on failure, and it ignores edge cases like toggling on already-3D layers or layers with existing 3D properties.

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%, with the enabled parameter already documented as 'true = 3D on, false = 2D'. The description adds no parameter meaning beyond the schema; it essentially restates the enabled semantics. Baseline 3 applies because the schema does the heavy lifting.

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 states a specific verb and resource: 'Enable or disable 3D mode on a layer.' It clearly communicates the toggle behavior and maps directly to the enabled boolean parameter. However, it does not explicitly differentiate itself from siblings like ae_set_layer_property, so it misses the top score.

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. The description gives no context about when toggling 3D mode is preferred over other layer mutations, and it names no sibling tools or exclusion conditions.

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