Skip to main content
Glama
rps321321

obsidian-mcp-pro

by rps321321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Insert at Section

insert_at_section

Add content to a specific section without replacing it. Choose placement before the heading, after the heading, or at the end of the section body.

Instructions

Insert content into a specific section without replacing it. position controls where: 'before' inserts above the heading, 'after-heading' inserts immediately under the heading line (at the top of the section body), 'append' inserts at the end of the section's body just before the next heading. Use to add a new bullet or paragraph without rewriting the section.

Input Schema

NameRequiredDescriptionDefault
pathYesVault-relative path to the note.
contentYesContent to insert. A trailing newline is normalized.
sectionYesHeading path identifying the section.
positionNoInsert before the heading line, immediately after the heading, or at the end of the section body.append

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / content / maxLength
      Added value: +1000000
  2. Addedv2.0.0
  3. Removedv1.9.0
  4. Addedv1.8.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare non-destructive, non-readonly and non-idempotent behavior, so the safety profile is covered. The description adds that content is inserted without replacement, which is useful context, but says nothing about failure modes (missing section) or repeated-insert behavior that the non-idempotent hint implies.

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?

Front-loads the core action, then the position semantics, then the use case. Every sentence contributes and there is no redundancy.

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?

No output schema exists, but the description covers action, positioning, and use context adequately. It omits what happens when the section is not found, a minor gap for an insertion tool.

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?

Schema coverage is 100%, so baseline is 3, but the description meaningfully elaborates the `position` enum in plain terms ('above the heading', 'top of the section body', 'just before the next heading'), adding clarity beyond the schema's own enum descriptions.

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?

States a specific verb+resource ('Insert content into a specific section') and immediately clarifies it does not replace the section, distinguishing it from update_section and append_to_note in the sibling list.

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?

'Use to add a new bullet or paragraph without rewriting the section' gives a clear use context and implicitly contrasts with update_section. It does not explicitly name an alternative tool or exclusions, keeping it just short of a 5.

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