Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by aniketbiswas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_note

Duplicate a note to a new path in your Obsidian vault while retaining the original file.

Instructions

Copy a note to a new location in the vault. The original note is preserved.

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": {
      "sourcePath": "<sourcePath>",
      "destinationPath": "<destinationPath>"
    },
    "name": "copy_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
overwriteNoWhether to overwrite if destination exists.
sourcePathYesPath of the note to copy.
destinationPathYesPath for the new copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the key fact that 'The original note is preserved,' which is a non-obvious behavior. However, it does not mention what happens if a file exists at the destination and overwrite is false, or whether intermediate directories are created, leaving some behavioral ambiguity.

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 two short, direct sentences that efficiently convey the core action and a critical side effect. Every word earns its place, with no fluff or repetition.

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?

For a simple copy operation with a well-defined schema, the description is adequately complete: it states the operation and that the original is preserved. The absence of an output schema is acceptable given the tool's simplicity, and the overwrite behavior is documented in the schema. Minor gaps like error handling on conflict are not critical.

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 covers all three parameters with clear descriptions (sourcePath, destinationPath, overwrite), achieving 100% schema_description_coverage. The description provides no additional parameter semantics, so it does not add value beyond the schema.

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 tool's function: 'Copy a note to a new location in the vault.' It specifies the verb (copy), the resource (note), and the outcome (new location), and it distinguishes itself from sibling tools like delete_note (which removes) and create_note (which creates new notes).

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?

The description provides no explicit guidance on when to use this tool versus alternatives such as create_note or update_note. It does not mention scenarios where copying is preferred or any exclusions, leaving the agent to infer usage from the tool name and purpose.

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