Skip to main content
Glama
AdrianV101

obsidian-pkm

by AdrianV101

vault_update_frontmatter

Update YAML frontmatter fields in existing Obsidian notes while preserving all other content. Add, change, or remove fields with validation against the note's type.

Instructions

Update YAML frontmatter fields in an existing note. Parses existing frontmatter, updates specified fields, preserves everything else. Set a field to null to remove it. Protected fields (type, created, tags) cannot be removed. Field values are validated against the note's type (e.g. task status must be: pending, active, done, cancelled; task priority must be: low, normal, high, urgent). Paths in this tool's output are formatted as markdown links [vault-relative-path.md](obsidian://...) so users can Cmd/Ctrl-click to open in Obsidian. Preserve the link form when relaying paths to the user; pass only the bracket text (e.g. 01-Projects/Foo/note.md) to other vault tools' path arguments, never the full markdown link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath relative to vault root (exact path required)
fieldsYesFields to update. Set value to null to remove a field. Arrays (like tags) are replaced wholesale.
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explains null-removal semantics, protected fields, validation rules (with concrete examples), and the markdown link output format, giving the agent comprehensive insight into expected behavior.

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 dense but every sentence earns its place, covering purpose, edge cases, validation, and output formatting. It is well-structured and front-loaded with the primary action.

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?

For a tool with only two parameters and no output schema, the description is remarkably complete. It addresses behavioral edge cases, parameter constraints, and cross-tool usage, leaving little ambiguity for an agent.

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?

The input schema already has 100% coverage for both parameters. The description adds meaningful context for the 'fields' parameter by specifying protected fields and validation against note type, going beyond the schema's basic null-removal and array-replacement notes.

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?

The description explicitly states 'Update YAML frontmatter fields in an existing note' with a specific verb and resource. It clearly distinguishes from sibling tools like vault_edit or vault_write by focusing solely on frontmatter and detailing its behavior (parses, updates specified fields, preserves everything else).

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?

The description implies the tool's specific use case for updating frontmatter, but it does not explicitly state when to use it over alternatives or provide exclusions. It does include cross-tool guidance on how to pass paths to other vault tools, which offers contextual usage hints.

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/AdrianV101/obsidian-pkm-plugin'

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