Skip to main content
Glama
Sign In
Obsidian Everywhere

Obsidian Everywhere

by junnnnnw00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Patch Section

patch_section
DestructiveIdempotent

Replace content under a specific heading in an Obsidian note, keeping the heading and other sections intact.

Instructions

Replace the content under one heading, preserving the heading and the rest of the 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>",
      "heading": "<heading>",
      "content": "<content>"
    },
    "name": "patch_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExisting note path, title, or alias.
contentYesNew Markdown section content.
headingYesHeading text, without # markers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations provide destructiveHint=true and idempotentHint=true. The description adds behavioral context by stating it preserves the heading and rest of the note, going beyond the annotations. However, it does not disclose edge cases like missing heading or multiple matches.

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, front-loaded sentence that efficiently conveys the core operation with zero wasted words.

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

Completeness4/5

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

Given three parameters, no output schema, and annotations present, the description covers the essential behavior. It lacks details on error handling (e.g., heading not found) but is adequate for a straightforward patch operation.

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 coverage is 100% with each parameter described clearly in the schema (e.g., 'Existing note path, title, or alias'). The description adds no additional parameter meaning beyond what the schema already provides.

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 'Replace the content under one heading, preserving the heading and the rest of the note' clearly states the specific verb (replace) and resource (content under a heading), distinguishing it from siblings like replace_text (global replacement) or append_to_note.

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 modifying a section under a heading but does not explicitly state when to use this tool vs. alternatives like replace_text or update_frontmatter. No exclusions or prerequisites are mentioned.

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