Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CERATOPS_BLENDER_EXECUTABLENoAbsolute path to the Blender executable. Required when Blender is not available as `blender` on `PATH`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
inspect_projectB

Read project counts, configuration, and active-job state without modifying it.

list_assetsC

List character and shot identities plus their explicit versions.

inspect_assetB

Read one asset's lifecycle state or one exact immutable version.

compare_asset_versionsC

Compare the metadata and artifact hashes of two exact asset versions.

promote_versionB

Approve an exact version at a named review gate without changing its bytes.

archive_versionC

Archive an unpromoted version while retaining every file and record.

import_character_referenceB

Copy reference images or files into a new immutable character version.

create_characterC

Create a deterministic character blockout, optionally from an exact reference version.

create_character_meshC

Create a mesh version from one exact character version.

retopologize_characterC

Create a non-destructive retopology version with a target face budget.

create_uv_and_materialsC

Create UVs and a material in a new look-development version.

groom_characterC

Create a groom from an appearance-approved exact source version.

rig_characterB

Create a rig from a groom-approved exact source version.

build_face_rigC

Create facial shape keys from a rig-approved exact source version.

render_character_reviewC

Render a review artifact in a new version for an explicit approval gate.

validate_characterC

Read and validate exact character lineage plus recorded artifact hashes.

create_shotC

Create a new shot layout with an explicit frame range.

assemble_shotC

Assemble exact character versions into a new shot version.

setup_cameraC

Create a camera version from one exact shot source.

light_shotC

Create a lit shot version using a fixed production preset.

animate_shotC

Create a deterministic blocking-animation version.

sync_lipsC

Apply explicit frame/value mouth cues to an exact shot version.

add_secondary_motionC

Add bounded procedural secondary motion in a new shot version.

render_shot_previewC

Render a review sequence into a new preview version.

render_shot_finalC

Render an animation-approved source into a new final-render version.

package_assetC

Package one exact character or shot version into a versioned ZIP.

package_episodeC

Package caller-selected exact shot versions into a versioned episode ZIP.

get_job_statusB

Read the persistent status and result of a long production job.

cancel_jobC

Request cancellation of an exact queued or running production job.

resume_jobB

Resume failed, cancelled, or interrupted work under the same stable job ID.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.9/5.0

Scored across 30 tools

Disambiguation4/5

Most tools have distinct purposes, but render_character_review, render_shot_preview, and render_shot_final could be confused despite different targets and gates. Creation tools (create_character, create_shot, setup_camera, etc.) are clearly differentiated by noun. Some overlap exists but descriptions help.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern, with verbs like create, inspect, list, compare, promote, archive, package, render, validate, get, cancel, resume. No mixed conventions or vague names.

Tool Count2/5

With 30 tools, the set is large and may overwhelm an agent or indicate over-specialization. While each tool has a clear purpose, the count feels heavy for a typical MCP server, and some tools could potentially be merged (e.g., render_* into a parameterized render tool).

Completeness5/5

The tool surface covers a comprehensive production lifecycle from creation, inspection, validation, promotion, packaging, rendering, to job management (status, cancel, resume). No obvious CRUD or lifecycle gaps for the domain of character and shot production.

Maintenance

ActivityMaintained
ResponsivenessNo issues