Skip to main content
Glama

close_day_note

DestructiveIdempotent

Cierra el día, igual que el botón «Cerrar día» de la app pero sin su asistente: registra el cierre, convierte los recordatorios con "⏰" en tareas con su hora y deja la nota de sólo lectura. Las tareas provisorias del día (get_declared_tasks) NO se crean al cerrar desde acá —en la app las confirma el asistente—: si hacen falta, create_task antes de cerrar. Para reabrirlo: reopen_day_note.

Fuera de Secondbrain: con ClickUp o Jira conectado, las tareas que crea el cierre suben allá.

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": {
      "date": "<date>"
    },
    "name": "close_day_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesFecha en formato YYYY-MM-DD
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.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds real value beyond that by disclosing the concrete effects (reminder-to-task conversion, note becoming read-only) and the external sync to ClickUp/Jira when connected. It does not, however, clarify whether the read-only lock is reversible or what the response returns, so it earns a solid middle score rather than the top.

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 purpose is front-loaded in the first clause, and the remaining sentences cover prerequisites, the inverse operation, and external side effects without filler. It is dense and slightly long for a two-parameter tool, but every sentence carries distinct information.

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 destructive, externally-syncing mutation tool, the description covers effects, prerequisites, the undo path, and out-of-Secondbrain behavior. With full schema coverage and no output schema, nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, with both date and workspace_id fully documented including format and fallback behavior when the token is workspace-scoped. The description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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?

States a specific verb and resource (closing the day note) and enumerates its concrete effects: registers the closure, converts '⏰' reminders into timed tasks, and makes the note read-only. It anchors the behavior to a known app button ('Cerrar día') and names the sibling that performs the inverse (reopen_day_note), so an agent can distinguish it without opening any schema.

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?

Gives explicit when/when-not guidance: provisional tasks from get_declared_tasks are NOT created by this call, and the agent must run create_task beforehand if they are needed. It also names reopen_day_note as the alternative for undoing the operation, leaving nothing to inference.

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