Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
cdeck_pairA

Pair with the Apple TV showing this 6-character code. name labels this TV locally (default 'tv'); use distinct names if you pair more than one TV.

cdeck_schemaA

The deck document format (schema v1) plus guidance on what makes a good deck. Read this before the first push.

cdeck_pushA

Push a deck to the paired TV. deck is the JSON document (object or JSON string) in the format from cdeck_schema(). Replaces whatever the TV is showing.

cdeck_statusB

When the TV's deck was last updated, and which item ids the viewer has checked off on the TV ('acks'). Use acks to complete/clear those items in their source before the next push.

cdeck_listA

List the TVs paired on this machine.

cdeck_unpairA

Forget a paired TV: revokes the push token server-side and removes it locally. The TV will show a new pairing code.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct action in the pairing/deck lifecycle: pair, list, unpair, push, status, and schema. The only potentially adjacent tools, cdeck_list and cdeck_status, are clearly separated as listing paired TVs versus inspecting deck update state and acks.

Naming Consistency5/5

All tool names use the same cdeck_ prefix and snake_case convention. The suffixes are concise and consistently readable, even when mixing verbs (pair, push, list) and noun-like tools (schema, status).

Tool Count5/5

Six tools is well-scoped for this server: pairing lifecycle, schema guidance, push, and status. No tool appears redundant or out of place.

Completeness4/5

The surface covers the core workflow: schema discovery, pairing, listing, unpairing, pushing a deck, and checking acks/status. A minor gap is the absence of a direct tool to read back the current deck, though status plus source-side ack handling may be sufficient for the intended workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues