Skip to main content
Glama

create_zettel

Creates a new atomic knowledge note in a markdown vault, capturing one insight with title, optional source, body, and connections. Returns the created note's file path.

Instructions

Create a new zettel (atomic knowledge note).

Zettels are stored in the Zettel/ directory (or as configured by the vault's type definition). Each zettel captures a single atomic insight.

Args: title: Title of the zettel (the atomic insight). short_title: Short slug for the filename (e.g. "attention-mechanism"). source: Optional source reference as a wikilink (e.g. "[[literature-note]]"). body: Optional body text elaborating on the insight. connections: Optional list of related note wikilinks (e.g. ["[[note-1]]", "[[note-2]]"]). extra_vars: Optional dictionary of additional template variables.

Returns: Result of the creation including the file path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNo
titleYes
sourceNo
extra_varsNo
connectionsNo
short_titleYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior3/5

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

Description discloses that files are stored in Zettel/ or per vault configuration, and that creation returns a result including the file path. It does not mention behaviors like duplicate-file handling, overwriting, or validation failures, which matters because no annotations are provided to cover mutation or safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured into purpose, storage context, Args, and Returns sections, front-loading the core purpose in the first sentence. It is somewhat lengthy, but each line serves a purpose for a 6-parameter tool.

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?

The description covers purpose, storage location, all parameters, and the return value, and an output schema exists to detail the result shape. It omits edge-case behaviors such as duplicate short_title collisions or directory auto-creation, which would fully round out the picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining every parameter, including examples and semantics: short_title is a filename slug, source and connections are wikilinks, extra_vars are template variables. This adds substantial meaning beyond raw JSON schema types.

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?

Description opens with 'Create a new zettel (atomic knowledge note)', naming a specific verb and resource. It further distinguishes the tool by stating zettels live in the Zettel/ directory and capture a single atomic insight, separating it from sibling create_* tools like create_daily_note or create_literature_note.

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?

Description gives clear context for when to use: it is for atomic knowledge notes stored in Zettel/ rather than daily notes, projects, or meetings. It does not explicitly name alternatives or state when not to use the tool, but the zettel-specific context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.