Skip to main content
Glama

Create Vintage Lens

create_vintage_lens

Apply a vintage analog-film aesthetic to any TOP by chaining barrel distortion, chromatic aberration, vignette, and film grain effects using era presets.

Instructions

Drape a vintage analog-film aesthetic over any TOP in one call. Chains barrel/pincushion lens distortion → chromatic aberration → vignette → film grain as four inline GLSL passes inside a new baseCOMP. Era presets (super8, vhs, 16mm, 80s_camcorder) load era-correct strength defaults; any per-param override wins. Returns a standard Layer 1 envelope with container path, node paths, output path, preview image, warnings, and the resolved strength values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent network where the vintage-lens container is created (default '/project1')./project1
nameNoName suffix for the baseCOMP (default 'vintage_lens').vintage_lens
source_top_pathYesPath of the existing TOP to grade (e.g. '/project1/render1').
eraNoEra preset that sets default strength values; per-param overrides win.super8
distortion_strengthNoBarrel-distortion coefficient (UV warped from center). Overrides preset.
ca_strengthNoRGB-split offset magnitude (radial from center). Overrides preset.
vignette_strengthNoEdge darkening amount; 0 disables. Overrides preset.
grain_amountNoPer-pixel noise amplitude. Overrides preset.
Behavior4/5

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

The description discloses behavioral traits beyond annotations: it chains four GLSL passes, uses era presets with per-param overrides, and returns a standard envelope. No contradictions with annotations.

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?

The description is a single well-structured sentence that conveys all essential information without redundancy. It is front-loaded with the main action and efficiently packs details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, the description adequately covers tool function, return values, and parameter interaction (presets and overrides). It is comprehensive for the tool's complexity.

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?

Parameter schema coverage is 100%, but the description adds meaning by explaining that era presets set default strengths and per-param overrides win. This clarifies parameter interaction beyond schema.

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 tool creates a vintage analog-film aesthetic on any TOP, describing the processing chain and return payload. It distinguishes itself from numerous similar create_* tools.

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?

The description provides clear context that the tool is for adding vintage film effects over any TOP, but does not explicitly state when not to use it or list alternatives. The context is sufficient given the tool's specific niche.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server