Skip to main content
Glama

get_recent_notes

Read-onlyIdempotent

Obtiene las últimas N notas diarias con resumen de IA y extracto de contenido (máx. 1000 chars por nota).

Usar para: ver qué pasó esta semana, revisar actividad reciente, entender el contexto de trabajo de los últimos días.
Para leer una nota completa: usar get_daily_note con la fecha específica.
Para buscar en el contenido: usar search_daily_notes.

Retorna: date, summary (resumen IA), content (extracto), has_intelligence.

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_recent_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDías hacia atrás (default: 7)
limitNoMáximo de notas (default: 7)
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.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's job is to add behavior beyond that — and it does, disclosing the 1000-character truncation per note and the exact returned fields including has_intelligence. What it omits is how days and limit interact and whether results are ordered or capped by the annotation-level defaults.

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 with the core behavior, then cleanly partitioned into use cases, alternatives, and return values. Every sentence earns its place and there is no redundant restatement of the tool name or annotations.

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

Completeness4/5

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

For a read-only, three-parameter list tool with no output schema, listing the returned fields (date, summary, content, has_intelligence) is exactly what the agent needs. The remaining gap is minor: it does not clarify how days and limit combine or what an empty result looks like.

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 coverage is 100% and each parameter already documents its type, range, and default, so the schema carries the load. The description only echoes the notion of 'N notes' and never explains the semantic difference between days (lookback window) and limit (max notes), adding little beyond the schema.

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 (retrieve the last N daily notes) plus the scope limits (AI summary, content excerpt capped at 1000 chars per note). It explicitly separates itself from get_daily_note (full note) and search_daily_notes (content search), so an agent can route correctly 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?

The 'Usar para' block gives concrete scenarios (what happened this week, recent activity, recent work context), and the following two lines name the alternatives with the exact condition that selects them. When-to-use, when-not-to-use, and alternatives are all present.

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