Skip to main content
Glama

get_reminders

Read-onlyIdempotent

Los recordatorios del workspace: los que van a sonar y los que ya sonaron.

Un recordatorio ocurre a una hora, no vence un día: a esa hora suena el
teléfono. Nace de una línea de la nota diaria («⏰ 15:30 — llamar a Ana»),
de una tarea creada con `remind_time`, o del bot de chat.

`status`: `pending` todavía no sonó, `sent` ya se mandó (`sent_channel`
dice por dónde), `cancelled` se dio de baja.

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

Input Schema

NameRequiredDescriptionDefault
desdeNoSólo los de este día en adelante, YYYY-MM-DD
limitNoMáximo (default: 50)
statusNoFiltrar por estado (default: todos)
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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine domain semantics beyond that: reminders correspond to a specific instant, they are produced from daily-note lines, tasks with remind_time, or the chat bot, and sent items carry a sent_channel. It does not mention ordering of results or pagination behavior beyond the schema's default limit.

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 opening sentence front-loads what the tool returns, followed by a conceptual clarification and then the status semantics. Three short paragraphs with no filler; slightly prose-heavy for a simple list tool but every sentence contributes.

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

Completeness3/5

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

There is no output schema, so the description has to carry return-value burden, and it only partly does: it explains what a reminder is and what status means, but not the fields of returned items (e.g. the reminder text or scheduled time) or result ordering. Adequate for calling the tool correctly, incomplete for interpreting results.

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 100%, so the baseline is 3. The description goes past the bare enum labels by explaining what each status means ('pending' has not fired yet, 'sent' was already delivered and identifies the channel, 'cancelled' was withdrawn), which helps an agent choose the right filter.

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?

States a specific verb+resource ('los recordatorios del workspace') and defines the concept precisely: a reminder fires at a time rather than expiring over a day. This conceptually separates it from agenda/calendar-style siblings, but no sibling is named explicitly, so an agent still has to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the note that a reminder 'no vence un día' hints this is not the day-based/agenda tool, and the three origin sources (daily-note line, task with remind_time, chat bot) suggest where reminders come from. There is no explicit when-to-use/when-not-to-use statement and no named alternative such as get_agenda.

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