Skip to main content
Glama
libra850
by libra850

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OBSIDIAN_VAULT_PATHYesThe path to your Obsidian vault
OBSIDIAN_TEMPLATE_DIRNoThe template directory name within your Obsidian vaultTEMPLATE

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_note_from_templateC

テンプレートを使用してObsidianノートを作成します

list_templatesB

TEMPLATEフォルダ内の利用可能なテンプレート一覧を取得します

read_noteC

Obsidianノートの内容を読み込みます

update_noteC

Obsidianノートの内容を更新します

list_tagsB

Obsidianボルト内のすべてのタグを一覧表示します

rename_tagC

Obsidianボルト内のタグを一括でリネームします

search_filesC

Obsidianボルト内のファイルとディレクトリを検索します

link_notesC

ノート間にウィキリンクを作成します

find_broken_linksB

壊れたリンクの検出と修復支援を行います

analyze_backlinksC

バックリンク分析とグラフ構造の把握を行います

create_mocC

Map of Contents(目次ノート)を自動生成します

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: analyze_backlinks focuses on graph analysis, create_moc generates navigation structures, create_note_from_template handles templated creation, find_broken_links detects issues, link_notes creates connections, list_tags and list_templates enumerate metadata, read_note and update_note handle content operations, rename_tag manages tags, and search_files finds files. The descriptions clearly differentiate these functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, such as analyze_backlinks, create_moc, find_broken_links, and update_note. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

Tool Count5/5

With 11 tools, this server is well-scoped for managing an Obsidian vault, covering key operations like note creation, reading, updating, linking, tagging, searching, and analysis. Each tool serves a specific purpose without redundancy, making the count appropriate for the domain.

Completeness4/5

The tool set provides comprehensive coverage for core Obsidian workflows, including note lifecycle (create, read, update), linking, tagging, searching, and analysis. A minor gap is the lack of a delete_note tool for full CRUD operations, but agents can work around this by using file system operations or other methods.

Maintenance

ActivityInactive
ResponsivenessNo issues