Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Metis — Obsidian Vault

_obsidian_vault

Resolves the configured Obsidian vault path to enable note-indexing tools to access .md notes, checking environment variables and config files.

Instructions

Resolve the configured Obsidian vault path, if one is set and valid.

Looks up the user's external Obsidian vault so note-indexing tools
(e.g. kg_index_notes) know where to read .md notes from. Checks the
METIS_OBSIDIAN_VAULT environment variable first, then the
integrations.obsidian_vault (or top-level obsidian_vault) key in
user-config.yaml.

Takes no arguments.

Returns:
    A Path to the vault directory if it is configured and exists on disk,
    otherwise None.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses lookup order (env var, config file) and return value (Path or None). No annotations exist, so description carries full burden, and it covers the read-only behavior well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Efficiently structured: states purpose, motivation, technical details, and return type. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a zero-parameter tool with output schema. Covers all necessary aspects: configuration sources, return behavior, and integration context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters, so default is 4. Description does not need to add parameter info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it resolves the Obsidian vault path, distinguishing it from note-indexing siblings like kg_index_notes. Uses specific verb 'resolve' and resource 'Obsidian vault path'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains it is used by note-indexing tools, providing context for when it might be called. Does not explicitly state when an agent should call it directly or mention alternatives, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server