Skip to main content
Glama
Sign In
after-effects-mcp-enhanced

after-effects-mcp-enhanced

by ku1x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

bridge-status

Check the connected Adobe After Effects application and its runtime version. Confirm AE is running and retrieve version details.

Instructions

Check the connected AE application and runtime version. Requires AE running; no visible panel is necessary.

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": "bridge-status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description must convey behavior. The verb 'Check' implies a read-only operation with no side effects. Explicitly stating 'no visible panel is necessary' clarifies it does not alter UI state. Could be more explicit about not modifying anything, but it's reasonably transparent.

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?

Extremely concise, two sentences. No filler or redundant information. Front-loaded with the primary purpose.

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 the simplicity of the tool (no parameters, simple status check), the description is complete. It explains the required condition (AE running) and a key detail (no panel needed). Omission of return format is acceptable since no output schema is provided and the purpose is obvious.

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

Parameters4/5

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

No parameters exist, so this dimension is not applicable. Baseline of 4 is appropriate; description adds no parameter-specific information because none exist.

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?

Clearly states the tool's function: checking the connected AE application and runtime version. No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides important usage context: requires AE running and notes that no visible panel is needed. Could mention when to use it (e.g., before other AE operations) but is sufficient.

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