Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by aniketbiswas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_note_from_template

Create new notes from built-in templates for meetings, projects, books, articles, people, recipes, or decisions. Add custom fields for tailored frontmatter.

Instructions

Create a new note using a built-in template. Available templates: meeting, project, book, article, person, recipe, decision.

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": {
      "template": "<template>",
      "title": "<title>"
    },
    "name": "create_note_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle for the new note.
folderNoFolder to create the note in.
templateYesTemplate to use.
customFieldsNoCustom fields to include in frontmatter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic action ('Create a new note') without mentioning return values, error handling, duplicate title behavior, or what content is included beyond the template. This is minimal and insufficient for a no-annotation tool.

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 sentence that front-loads the core action and then lists the available templates. Every word earns its place, with no fluff or repetition of schema 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 relatively simple with an output schema absent and no annotations, but the description covers the core purpose. It lacks guidance on what happens after creation (e.g., return value) or how customFields interact with templates, so it is complete enough for basic use but leaves gaps for an agent needing robust expectations.

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 schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond the schema; it merely repeats the template enum values, which are already present in the schema. Therefore it neither improves nor worsens parameter understanding.

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 creates a new note using a built-in template and explicitly lists the available templates. This specific verb+resource distinction sets it apart from siblings like create_note, create_meeting_note, and list_templates.

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?

The description gives clear context by indicating this tool is for template-based note creation and enumerates the templates, but it does not explicitly name alternatives or exclusions (e.g., when to use create_note or create_meeting_note instead). Thus it has clear context without exclusions.

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