Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.system.status

Checks whether Adobe After Effects is installed, reports its version, and verifies bridge availability so you can confirm the automation connection before running commands.

Instructions

Check After Effects installation status, version, and bridge availability.

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": "ae.system.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkBridgeNo

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 are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the noun phrase. 'Check' implies a read-only probe, but it never says whether the probe launches or connects to a bridge process, how long it may block, whether it is safe or cheap to call repeatedly, or what a failure looks like. For a zero-annotation tool this is thin.

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 no filler, hedging, or redundant restatement of the tool name. Every word earns its place, though the brevity comes at the cost captured in the other dimensions.

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 is simple (one optional boolean, no nested objects, no output schema), so a short description is defensible, and the three things checked are enumerated. Still missing is any indication of the shape of the result (version string, status value, bridge reachability) and the behavior of the sole flag, which matters for a prerequisite-diagnostic an agent will call before other work.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter (checkBridge, boolean, default true) with 0% schema description coverage, so the description must explain it; it only gestures at it with the phrase 'bridge availability'. It never says what setting checkBridge=false skips, whether true incurs a connection attempt or latency, or what the default implies — the caller cannot tell the practical difference between the two values.

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?

States a specific verb (Check) plus three named resources: After Effects installation status, version, and bridge availability. This is clearly distinguishable from sibling ae.render.status, which deals with rendering rather than installation/health. It stops short of explicitly naming that sibling to contrast with, so not a 5.

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?

Usage is only implied: a diagnostic an agent would call to verify the host app is present and the bridge is reachable before running other ae.* operations. There is no explicit when-to-use, no when-not-to-use, and no mention of which sibling to call instead if the check fails.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.