Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPLATMAKER_ENGINENoSelects which splat generation engine is configured (e.g. Nerfstudio). Set once an engine is chosen; reported by the splat_engine_status tool.

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
splat_generateA

Generate or inspect a Gaussian-splat world from local media.

Operations: from_video - start a job from a video file (video_path required) from_images - start a job from a set of images (image_paths required) status - check a job's status (job_id required) list - list all known jobs get_asset - return asset paths for a completed job (job_id required)

from_video/from_images return IMMEDIATELY with status="running" - the real ns-process-data -> ns-train -> ns-export pipeline runs as a background task (real training takes real minutes, not seconds). Poll with operation="status" until status is "done" or "failed".

Return Format

Always a dict with a success bool and a human-readable message. Success paths also carry the documented payload keys (job_id, status, jobs, asset_paths). Error paths carry success: False plus an error key with the machine-readable reason; the error key is kept for backward compatibility with existing clients.

Examples

splat_generate(operation="from_video", video_path="D:/cap/walk.mp4") -> {"success": True, "job_id": "...", "status": "queued", "message": ...} splat_generate(operation="status", job_id="<id>") -> {"success": True, "job_id": "<id>", "status": "running", "message": ...} splat_generate(operation="list") -> {"success": True, "jobs": [...], ...}

splat_engine_statusA

Report which splat engine is configured and whether the real CLI tools are actually present (requires uv sync --extra engine).

Return Format

{"success": True, "engine": str, "configured": bool, "max_iterations": int, "note": str, "message": str, "verified": "pending"|"ok"|"broken"|"missing", "engine_version": str, "engine_error": str} — message mirrors note so fleet tooling can render the result without special-casing it. configured is the fast exe check; verified is the cached ns-train --help truth (pending until the background probe lands).

Examples

splat_engine_status() -> {"success": True, "engine": "nerfstudio", "configured": True, "max_iterations": 15000, "note": ..., "message": ...}

server_shutdownA

Gracefully shut down this server. Matches the REST /api/shutdown endpoint - both call the same underlying implementation.

Return Format

{"success": True, "status": "shutting_down", "message": str}.

Examples

server_shutdown() -> {"success": True, "status": "shutting_down", "message": "Server will exit in ~0.5s"}

show_status_cardA

Show splatmaker engine + job-queue status as a rich Prefab card.

Return Format

A ToolResult with plain-text content (same numbers as the card) and structured_content carrying the PrefabApp view for Prefab-capable hosts.

Examples

show_status_card() -> card with engine state, job counts by status, backend port.

Prompts

Interactive templates invoked by user choice

NameDescription
splat_workflowGuided prompt: capture -> generate -> poll -> collider mesh. ## Return Format A plain-text workflow briefing the caller pastes into the session. ## Examples `splat_workflow` -> multi-step instructions for a from_video job.

Resources

Contextual data attached and managed by the client

NameDescription
jobs_resourceLive job ledger (same rows as GET /api/jobs). ## Return Format JSON array of {job_id, kind, status, created_at, message}. ## Examples Read `splatmaker://jobs` -> current ledger without calling list.

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation3/5

splat_generate multiplexes five operations (create, status, list, get_asset) while show_status_card and splat_engine_status both report engine/job state, so an agent can plausibly reach for splat_generate(operation='status') or show_status_card for the same information. The descriptions distinguish them somewhat (card vs. raw status), but boundaries are soft.

Naming Consistency4/5

All names are snake_case and readable; two share the splat_ prefix while server_shutdown and show_status_card do not, and verbs vary (generate, status, shutdown, show). Minor deviation from a strict verb_noun pattern but nothing confusing.

Tool Count4/5

Four tools is a tight surface, but splat_generate absorbs five operations internally, so the effective capability set is reasonable for a focused splat-generation server. Nothing feels padded, though the count is on the low side.

Completeness3/5

The pipeline lifecycle is covered end to end: start job, poll status, list jobs, fetch assets, plus engine diagnostics. However there is no cancel/delete job operation and no way to inspect a job's logs or failures, which are meaningful gaps for long-running background jobs.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues