Skip to main content
Glama

write_note

Save or overwrite a complete note in the knowledge vault using title, content, and category. Use it to store new content or fully replace an existing note.

Instructions

Crear, guardar, anotar, añadir o actualizar una nota en la base de conocimiento (la bóveda). Operación de escritura — úsala cuando quieras guardar contenido nuevo o sobrescribir uno existente, incluyendo notas en la carpeta bandeja-de-entrada. Si la nota ya existe, la actualiza completa (sobrescribe el cuerpo entero). Para retoques puntuales sin reenviar todo, prefiere edit_note, append_to_note, prepend_to_note, update_section o insert_after_section. Usa "name" para actualizar una nota existente por su slug real (útil cuando el título nuevo difiere del nombre de archivo).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSlug del archivo existente a actualizar (sin extensión .md). Úsalo cuando el título no coincide con el nombre de archivo actual. Si se omite, el slug se genera automáticamente desde el título.
tagsNoEtiquetas para el frontmatter YAML. Opcional y desaconsejado: los editores que agrupan por etiqueta no leen el frontmatter, así que la clasificación se pone como hashtags #snake_case en la última línea del cuerpo. Si se omite, no se escribe el campo.
titleYesTítulo de la nota
contentYesContenido en Markdown, sin incluir frontmatter ni el título h1
categoryYesSubcarpeta donde guardar la nota (p. ej. "proyectos", "clientes/nombre-cliente" o "conocimiento/problemas-resueltos"). La estructura de carpetas es libre: usa las categorías que tu trabajo pida. Para ver las que ya existen, usa get_index.
Behavior4/5

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

Discloses that the tool overwrites the entire body if the note exists. No side effects or permissions mentioned, but for a write operation without annotations, this is fairly transparent.

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?

Two well-organized paragraphs. First paragraph states purpose and usage guidelines, second explains parameters. No fluff; every sentence adds value.

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

Completeness5/5

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

Given 5 parameters all documented in schema, and no output schema, the description provides sufficient context. It references related tools for partial updates and explains key behaviors like overwriting.

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?

Schema already describes all parameters (100% coverage). Description adds valuable context: explains when to use 'name' (slug for existing notes), warns that 'tags' is discouraged, and suggests using get_index for categories.

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 that the tool creates, saves, annotates, adds, or updates a note in the knowledge base. It specifies it is a write operation for new or overwritten content, and distinguishes from sibling tools for partial updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (save new or overwrite existing) and when not (for small tweaks, prefer specific tools like edit_note, append_to_note, etc.). Also provides guidance on using the 'name' parameter for existing notes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jmpdsevilla/BovedIA'

If you have feedback or need assistance with the MCP directory API, please join our Discord server