Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key created in your Cotlet.dev console. Required to call the local wrapper helpers and used as the bearer token for Codex and Claude Code.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

oto.photo through Cotlet.dev. Call oto_photo_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

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
oto_photo_guideA

How to work in oto.photo (organise galleries, bookings, clients, gift certificates and portfolio albums): its screens and the sign-in link. Call this first.

oto_photo_statusA

Check that your Cotlet.dev account and oto.photo are ready: account, credits and oto.photo connection.

oto_photo_openB

Open a oto.photo page in your signed-in Cloud Browser (default https://oto.photo/auth) to work with organise galleries, bookings, clients, gift certificates and portfolio albums.

oto_photo_readA

Read the current oto.photo page: its text and numbered buttons, links and fields.

oto_photo_clickC

Click a numbered element on the current oto.photo page.

oto_photo_typeB

Type text into a numbered field on the current oto.photo page.

oto_photo_closeA

Close the oto.photo browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

The core action tools (open, read, click, type, close) are clearly distinct, and guide vs status are separated by their descriptions (instructions vs account/credit check). There is mild conceptual overlap between read, guide and status as all returning information, but the descriptions resolve it.

Naming Consistency5/5

Every tool follows the same oto_photo_<verb> snake_case pattern with short, concrete verbs. No mixed conventions or vague naming.

Tool Count5/5

Seven tools is well-scoped for a browser-driven site controller: session lifecycle, page inspection, and two input primitives plus help/status. Each tool earns its place with no redundancy.

Completeness3/5

The basic interaction loop (open, read, click, type, close) plus guide/status is covered, but there is no scrolling, navigation/back, waiting for loads, or dropdown/checkbox handling, which are likely needed for gallery, booking and client workflows. Photo/album management arguably also implies upload/delete affordances not present.