Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PET_USB_PORTNoSet this when more than one USB serial device is plugged in, to select the port used by the esp32-pet MCP server.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
bip_set_stateB

Set BIP's physical facial expression, eye gaze direction, speaking mouth animation, or trigger an expressive blink over USB Serial.

bip_play_timelineC

Play a sequence of time-coded facial animation keyframes on BIP (non-blocking firmware loop).

bip_speakC

Speak English text aloud on Mac and synchronize BIP's mouth, gaze, and blinks to the audio duration.

bip_get_statusA

Return BIP's current expression state, USB port, Wi-Fi IP, and recent physical button presses.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinguishable action: setting a single state, playing a keyframe timeline, reading status, and speaking text. There is mild overlap since bip_set_state also controls speaking mouth animation while bip_speak synchronizes mouth/gaze/blink, so an agent might hesitate over which to use for mouth motion, but the descriptions clarify the intended split.

Naming Consistency5/5

All four tools use a consistent snake_case pattern with the shared 'bip_' prefix and a verb-led name (set_state, play_timeline, get_status, speak). The convention is predictable and readable across the whole surface.

Tool Count4/5

Four tools is on the lean side but each covers a distinct facet (state, sequence playback, status, speech) of driving a physical pet device. It is slightly thin — no separate stop/reset tool — but nothing feels redundant.

Completeness3/5

The core actions (set expression, play animation, speak, read status) are covered, but there is no way to stop or interrupt a running timeline, reset to a known idle state, or enumerate valid expressions/gazes. These gaps will force agents to improvise when recovering from an animation or discovering valid state values.

Maintenance

ActivityMaintained
ResponsivenessSyncing