oh-my-cassette
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cassette_bridge_statusA | Check whether the Cassette backend is reachable and compatible. Waits briefly for a reconnect. The editing tools are only listed while the backend is connected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one exposed tool, there is no possibility of confusion about which tool to select. Its purpose (connectivity/compatibility check for the Cassette backend) is explicit and unambiguous.
The single name cassette_bridge_status is descriptive, snake_case, and readable, but follows a noun_phrase convention rather than a verb_noun action pattern. With only one name, consistency cannot really be violated, so this is a minor deduction at most.
A single gate/status tool is thin for a server whose apparent domain is cassette editing; the description admits the real editing tools only appear once the backend connects. The surface as listed is one trivial check.
The server's stated purpose (editing cassettes) has no create/read/update/delete operations exposed at all — only a reachability check. This is a severely incomplete surface that would block any actual work.