Skip to main content
Glama

get_daily_note

Read-onlyIdempotent

Obtiene la nota diaria de una fecha (default: hoy). Las notas diarias son el log del día: lo que pasó, tareas, conversaciones, ideas.

Retorna:
- date: fecha de la nota
- content: contenido completo en texto plano (máx. 8000 chars)
- summary: resumen generado por IA (analysis_summary), puede estar vacío si no se analizó
- intelligence: índice de inteligencia/productividad del día (null si no calculado)

Si no existe nota para esa fecha, retorna un mensaje indicándolo.
Para buscar en notas de varios días, usar search_daily_notes o get_recent_notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_daily_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFecha en formato YYYY-MM-DD (default: hoy)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds real information: the 8000-char content cap, that summary may be empty if analysis never ran, that intelligence may be null, and that a missing note returns an explanatory message rather than an error. The only gap is nothing about pagination/truncation behavior when content exceeds 8000 chars.

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?

Front-loaded purpose sentence, then a scannable field-by-field return block, then a fallback-case line and the sibling routing line. Every sentence carries distinct information; none restates the tool name or the schema verbatim.

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?

No output schema exists, and the description compensates fully by enumerating the four returned fields with their types and null/empty conditions. Combined with the missing-note behavior and the cross-day alternative, an agent has everything needed to call this correctly and interpret the result.

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% and both parameters already document format and the omit-means-all-workspaces behavior, so the baseline is 3. The description reinforces the date default ("default: hoy") but adds no new syntax or semantics beyond the schema, and says nothing about what the date parameter does at timezone boundaries.

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?

Opens with a specific verb+resource ("Obtiene la nota diaria de una fecha") and immediately defines what a daily note is ("el log del día: lo que pasó, tareas, conversaciones, ideas"), so the agent knows the content model, not just the name. It also explicitly separates this single-date read from the bulk alternatives search_daily_notes and get_recent_notes.

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?

States the default (today) and explicitly routes multi-day lookup to sibling tools: "Para buscar en notas de varios días, usar search_daily_notes o get_recent_notes." That is a concrete when-to-use-this vs when-to-use-another rule, not an inferred one.

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