Skip to main content
Glama

write_daily_note

Destructive

Escribe o agrega contenido a la nota diaria del workspace.

Por defecto AGREGA al final de la nota existente (append=true). Usar append=false solo para reemplazar todo el contenido.

Acepta markdown (títulos, negritas, listas, tablas, citas, código) y lo convierte a formato del editor.
Cada renglón es un bloque propio: dos renglones seguidos NO se juntan en un párrafo, así que
un recordatorio (⏰ 15:30 — …) o una tarea (✅ …) por renglón se siguen leyendo uno por uno.
Si la nota no existe para esa fecha, se crea nueva.

Usar para: registrar lo que pasó hoy, anotar ideas, documentar reuniones, agregar tareas al log del día.

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": {
      "content": "<content>"
    },
    "name": "write_daily_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFecha YYYY-MM-DD (default: hoy)
appendNotrue (default) = agrega al final de la nota existente. false = reemplaza todo el contenido
contentYesTexto a escribir en la nota (markdown; un bloque por renglón)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description explains the destructive default (append=true appends, append=false replaces everything), matching and clarifying the destructiveHint=true annotation. It adds non-obvious behavior the annotations cannot convey: markdown is converted to editor format, each line becomes its own block so consecutive lines are not merged, and a new note is created if none exists for that date.

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?

Front-loaded with the core action and the append default before the detail. The markdown/block explanation is longer than strictly necessary but earns its place by preventing malformed notes. Some sentences could be tightened without loss.

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?

For a write tool with no output schema and a destructive annotation, the description covers the essentials an agent needs: default mode, replacement risk, format handling, line semantics, and auto-creation. Return values are not described, but that is a minor gap given no output schema exists.

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 already 100%, so the baseline is 3, but the description adds real meaning: the default and destructive consequence of append, and the per-line block semantics of content. It adds nothing extra for date or workspace_id beyond the schema, keeping it below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb pair and resource: 'Escribe o agrega contenido a la nota diaria del workspace.' It is immediately clear this is the write path for the daily note. It does not name the read counterpart (get_daily_note) to route the agent explicitly, so it stops short of full sibling differentiation.

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 'Usar para:' list gives concrete use cases (logging the day, ideas, meetings, task log), and the description constrains the risky mode with 'Usar append=false solo para reemplazar todo el contenido.' It never states when NOT to use it or points to an explicit alternative such as get_daily_note for reading.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources