Skip to main content
Glama

cronos_prepara_domani

Prepares the next working day's folder by creating a todo.md file with provided content and a raw.md skeleton if not existing. Supports specifying a target date.

Instructions

Prepara la cartella del prossimo giorno lavorativo con todo.md e scheletro raw.md.

Default: il giorno target e' calcolato come prossimo giorno lavorativo da oggi (lun-gio -> +1, ven -> lun, sab -> lun, dom -> lun). In alternativa si puo' specificare una data esplicita per pianificare un giorno futuro qualsiasi.

Comportamento:

  • Crea/sovrascrive todo.md con contenuto_todo (un to-do e' l'ultima pianificazione, non un log progressivo).

  • Crea raw.md con lo scheletro standard SOLO se non esiste gia', per non sovrascrivere entry aggiunte in anticipo.

Usa questo tool:

  • Al termine di cronos_scrivi_fine_giornata, per impostare il todo del giorno successivo a partire dai punti aperti della giornata.

  • Manualmente quando vuoi pianificare le cose da fare in un giorno futuro.

Parametri:

  • contenuto_todo (str, required): Contenuto markdown completo di todo.md

  • data (str, optional): Data target YYYY-MM-DD (default: prossimo giorno lavorativo)

Restituisce: Conferma con path di todo.md e raw.md, e flag se raw e' stato creato.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contenuto_todoYesContenuto markdown completo del file todo.md
dataNoData target YYYY-MM-DD (opzionale, default: prossimo giorno lavorativo)
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: todo.md is always overwritten, raw.md is created only if not exists, default date logic (weekday calculation), and optional explicit date. It also describes the return value.

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 well-structured with sections for default, behavior, usage, and parameters. It is concise yet comprehensive, using bullet points effectively.

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?

The description covers all necessary aspects: purpose, behavior, parameter details, default calculation, and return value. It is complete for a tool with no output schema and moderate complexity.

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%, so baseline is 3. The description adds minimal extra context beyond the schema: it explains the default date logic but does not significantly enhance parameter meaning.

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 prepares the next working day's folder with todo.md and raw.md skeleton. It specifies the exact files created and the conditional behavior, differentiating it from sibling tools like cronos_scrivi_fine_giornata.

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 explicitly states when to use this tool: after cronos_scrivi_fine_giornata or manually for future planning. It provides clear context but does not explicitly mention when not to use it.

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/mauriziomocci/mcp-cronos'

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