Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TENNIS_EVOLUTION_LICENSENoOptional Pro license key. Can alternatively be activated with `tennis-evolution license activate te1.xxxxx`. Used to remove the watermark and allow unlimited highlight segments.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
probe_videoA

Read duration, resolution, rotation, HDR/colour, audio tracks and recording time of a local video file. Run this first to confirm the file is readable.

rank_highlightsB

Parse a rally list and show which rallies would be kept, so the user can confirm before rendering.

start_highlight_reelA

Start the full pipeline in the background: lossless keyframe-aligned clips, a plain reel, a labeled reel (hit count / venue / wall clock / source timestamp) and manifest.json with self-check results. Returns a job_id; poll get_job. A 47-minute iPhone HDR recording with 5 rallies takes 3-5 minutes on an M-series Mac.

get_jobA

Status of a job from start_highlight_reel: running/done/failed, the last log lines, and once done the manifest (outputs and verification).

verify_videoC

Clean decode, zero start offset, A/V duration match, non-black first/last frame, non-silent audio.

license_statusA

Whether a Pro licence is active, the free-tier limits and the pricing URL.

activate_licenseC

Verify a te1.… key offline and store it for future renders.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Most tools occupy clearly different stages of the pipeline (probe, rank, render, poll, verify, license). The only real friction is probe_video vs verify_video, which both inspect a video file; the descriptions differentiate them (metadata read vs quality checks) but an agent could still reach for the wrong one.

Naming Consistency4/5

Nearly all names follow a consistent snake_case verb_noun pattern (probe_video, rank_highlights, start_highlight_reel, get_job, verify_video, activate_license). The one deviation is license_status, which omits the verb, though its meaning remains obvious.

Tool Count5/5

Seven tools is a tight, well-scoped set for a video highlight pipeline, with each tool earning its place. Nothing feels redundant or padded.

Completeness4/5

The core lifecycle is covered: probe, preview ranking, start render, poll status, verify outputs, plus licence gating. Gaps exist for a long-running job server, notably no cancel/abort and no way to list past jobs or outputs, which agents would have to work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues