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

Tools

Functions exposed to the LLM to take actions

NameDescription
ask_web_chatB

Envia consulta para um chat web autenticado via Chrome CDP local (127.0.0.1:9222) com sanitizacao previa e fila por provedor.

list_chat_sessionsB

Lista todas as sessoes ativas, abas ocupadas e leases em andamento.

cancel_chatA

Interrompe a execucao ou streaming de resposta de uma sessao em andamento.

chat_bridge_statusB

Retorna informacoes de status da conexao CDP 127.0.0.1:9222, estado das filas e auto-diagnostico doctor opcional.

preview_payloadA

Modo dry-run para inspecao de segredos, PII, arquivos proibidos e tamanho antes do envio.

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 5 tools

Disambiguation4/5

Each tool targets a distinct operation: sending queries, listing sessions, cancelling work, checking bridge status, and dry-run preview. The main possible confusion is between list_chat_sessions and chat_bridge_status, since both expose queue/session state, but descriptions clarify their different focus.

Naming Consistency4/5

Most tools follow a verb_noun pattern (ask_web_chat, list_chat_sessions, cancel_chat, preview_payload). chat_bridge_status is a noun phrase and breaks the pattern slightly, but the overall convention remains predictable.

Tool Count5/5

Five tools is well-scoped for a chat bridge server. Each tool covers a meaningful lifecycle action without redundant surface area.

Completeness4/5

The surface covers sending, listing, cancelling, status, and dry-run inspection, which are the core operations for an authenticated web chat bridge. Minor gaps exist around explicit session cleanup or history retrieval, but agents can likely work around them.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues