Skip to main content
Glama
Sign In
Another bloated Obsidian MCP Server

Another bloated Obsidian MCP Server

by diegorv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_frontmatter_field

Delete a specific field from a note's frontmatter to clean up metadata. Provide the note path and field name to remove.

Instructions

Remove a specific field from the frontmatter of 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": {
      "path": "<path>",
      "field": "<field>"
    },
    "name": "remove_frontmatter_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the note
fieldYesName of the field to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool removes a field, implying mutation, but does not disclose edge-case behavior such as what happens if the field does not exist, whether the operation is idempotent, or if it modifies the note file in place.

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, well-structured sentence that front-loads the verb and is free of fluff. Every word contributes to the meaning.

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

Completeness2/5

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

Although the tool is simple, the description provides only the basic action with no usage context or behavioral detail. Given the lack of annotations and the existence of closely related sibling tools, the description is insufficient for an agent to fully understand its behavior and appropriate use.

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?

The input schema fully describes both parameters (path and field) with the schema coverage at 100%. The description adds no additional semantic value beyond the schema, so the baseline score of 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 states the action ('Remove') and the target ('a specific field from the frontmatter of a note'). It is specific and distinguishes from sibling tools like remove_from_array_field by focusing on a field rather than an array element.

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 such as update_frontmatter or remove_from_array_field. The description only states what it does, not when it is appropriate.

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