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
batman_loginC

Fazer login na API Batman

batman_registerC

Registrar novo usuário na API Batman

batman_get_current_batmanB

Obter o Batman e Robin atuais

batman_get_developersC

Listar todos os desenvolvedores

batman_get_developerB

Obter um desenvolvedor específico

batman_create_developerC

Criar um novo desenvolvedor

batman_update_developerD

Atualizar um desenvolvedor

batman_delete_developerC

Remover um desenvolvedor

batman_get_unavailabilitiesC

Listar indisponibilidades

batman_create_unavailabilityD

Criar uma nova indisponibilidade

batman_get_priority_detailsC

Obter detalhes do cálculo de prioridade

batman_assign_batmanD

Atribuir o Batman atual

batman_get_historyC

Obter histórico de Batmans

batman_recalculate_prioritiesC

Recalcular prioridades dos desenvolvedores

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource and action. Developer CRUD, unavailability list/create, and Batman assignment/history/priority operations are clearly separated, with no overlapping purposes.

Naming Consistency4/5

All tools use a consistent batman_ prefix and follow a verb_noun pattern, but there are minor inconsistencies such as mixed singular/plural nouns (e.g., get_developers vs get_developer) and compound verb forms (get_current_batman, recalculate_priorities).

Tool Count5/5

14 tools is well within the ideal range and each tool serves a specific function in managing developers, unavailability, and Batman assignments.

Completeness4/5

The developer lifecycle is fully covered with CRUD, but unavailability is missing update and delete operations, representing a minor gap in the otherwise complete workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues