Skip to main content
Glama

Metis · Librarian — Export Knowledge Markdown

export_knowledge_markdown

Export your library as a cross-linked Obsidian-style Markdown vault. Creates one note per item with YAML frontmatter and abstract, plus an index, connected by wikilinks for shared tags.

Instructions

Export the library as a cross-linked Obsidian-style Markdown vault.

Writes one Markdown note per library item (YAML frontmatter + abstract) plus
an index, with [[wikilinks]] between items that share a tag — the
claude-obsidian / LLM-Wiki pattern. Gives you a portable, human-readable,
git-diffable view of the knowledge graph you can open in Obsidian. Read-only
on the database; writes only Markdown.

Args:
    out_dir: Destination folder. Default: outputs/knowledge-export/ under the RC root.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
out_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description explicitly states 'Read-only on the database; writes only Markdown', which clarifies safety and side effects. It also describes the output format. However, it does not mention potential issues like overwrite behavior or performance with large libraries.

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?

The description is concise (about 120 words) and well-structured: purpose, format, portability, safety, and parameter. Every sentence adds value without redundancy.

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?

Given the tool's simplicity and the presence of an output schema, the description covers all critical aspects: what it does, output format, side effects, and parameter description. No missing essential information.

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?

With 0% schema coverage, the description compensates by explaining the single parameter 'out_dir' with a default path. It adds meaning beyond the schema, though it could elaborate on what 'RC root' means and behavior when omitted.

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

Purpose4/5

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

The description clearly states the tool exports the library as a cross-linked Markdown vault with specific details (YAML frontmatter, index, wikilinks). However, it does not explicitly differentiate from the sibling tool '_obsidian_vault', which may have similar functionality.

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

Usage Guidelines3/5

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

The description implies usage for creating a portable Markdown export but lacks explicit guidance on when to use this tool vs alternatives, such as other export or search tools. No 'when not to use' or alternative recommendations are provided.

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