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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
obsidian_search_notesC

Recherche ciblée et filtrée à travers les notes du coffre Obsidian de Noa

obsidian_read_noteB

Lit et extrait le contenu complet d'une note Obsidian avec séparation du frontmatter YAML

obsidian_append_journalA

Insère une entrée quotidienne structurée dans 03 - Vie Perso/Journal de Bilan.md en tête de l'historique

obsidian_add_backlog_taskA

Ajoute une action à cocher dans 03 - Vie Perso/Backlog.md sous le niveau de priorité et le domaine choisis

obsidian_get_mocB

Extrait les notes interconnectées depuis l'un des 7 Hubs/MOCs du coffre

system_inspect_portB

Inspecte quel processus (PID et nom) écoute sur un port TCP local donné

system_free_portB

Arrête proprement le processus bloquant un port TCP local (avec garde-fou de sécurité protégeant les processus système vitaux)

git_health_auditA

Déclenche un audit de santé et d'hygiène complet d'un dépôt Git local via repo-doctor (score 0-100, grade, piliers et remédiations)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource and action: note reading/searching, journal appending, backlog task creation, MOC extraction, port inspection, port freeing, and git auditing. The only close pair is system_inspect_port vs system_free_port, but inspect vs. free is clearly separated by read-only vs. mutating semantics.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern with domain prefixes (obsidian_, system_, git_). The prefixes make grouping predictable and the action names are readable throughout.

Tool Count5/5

Eight tools is a well-scoped set for a personal cockpit covering Obsidian, local system ports, and git hygiene. Each tool maps to a concrete workflow rather than being redundant or filler.

Completeness3/5

The Obsidian surface covers read/search plus narrow write workflows (journal append, backlog add), but lacks generic note creation, update, or deletion, which are common expected operations. System and git sides are intentionally narrow, so an agent can hit dead ends when asked to perform broader note or repository actions.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues