Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, used for authorization to the hosted MCP server and local bridge.

Instructions

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

RunLoyal through Cotlet.dev. Call runloyal_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
runloyal_guideA

How to work in RunLoyal (pet counts, boarding bookings, report cards, owner messages and invoices): its screens and the sign-in link. Call this first.

runloyal_statusA

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

runloyal_openA

Open a RunLoyal page in your signed-in Cloud Browser (default https://www.runloyal.com) to work with pet counts, boarding bookings, report cards, owner messages and invoices.

runloyal_readB

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

runloyal_clickC

Click a numbered element on the current RunLoyal page.

runloyal_typeC

Type text into a numbered field on the current RunLoyal page.

runloyal_closeA

Close the RunLoyal 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.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct phase of work: guide (docs), status (account/credit readiness), open (navigation), read (page inspection), click/type (interaction), close (teardown). The numbered-element model in read/click/type makes their boundary explicit and non-overlapping. Guide vs. status are the closest pair but differ clearly (domain how-to vs. connection/credits health).

Naming Consistency4/5

All seven tools share the runloyal_ prefix in snake_case, which is highly predictable. Minor deviation: 'guide' and 'status' are nouns while the rest are imperative verbs (open, read, click, type, close).

Tool Count5/5

Seven tools is a tight, well-scoped surface for a browser-automation wrapper — one setup/diagnostic pair, one navigation pair, two interaction primitives, and a cleanup tool. No redundant or speculative tools.

Completeness4/5

Open/read/click/type/close plus read/status covers the core browser loop and lets agents avoid dead ends on most flows. Gaps remain for common interactions: no keyboard/Enter or form-submit primitive, no dropdown-select, and no scroll or wait for long or asynchronously loading pages.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues