Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

obsidian_property_set

Set a frontmatter property on an Obsidian note by specifying the file path, property key, and value to update or add metadata.

Instructions

Set a frontmatter property on a note

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "obsidian_property_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesProperty key to set
fileYesFile path (relative to vault root)
valueYesProperty value to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose whether setting an existing property overwrites it, whether the file must exist, or what happens if the note is missing. For a mutation tool, this lack of behavioral context is a gap.

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 a single, direct sentence that immediately conveys the tool's purpose. It is front-loaded and contains no filler or redundant information.

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

Completeness3/5

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

The tool is simple with 3 required parameters fully documented in the schema. However, because it is a mutation tool with no annotations and no mention of overwrite behavior or file existence requirements, the description is minimally viable but not fully complete.

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

Parameters3/5

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

Schema description coverage is 100%, with each parameter (file, key, value) individually described in the schema. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly identifies the action ('Set') and the resource ('a frontmatter property on a note'). It distinguishes from sibling tools like obsidian_properties (list properties) and obsidian_tags_rename (rename tags) by specifying the property-setting operation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention when to prefer obsidian_property_set over obsidian_properties or other obsidian tools, nor any prerequisites or conditions.

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

Deploy Server

Other Tools