Skip to main content
Glama

list_reminders

Read-only

Retrieve reminders sorted by due date from one list or all lists, filtered by completion status and due date range, so you can review upcoming tasks.

Instructions

List reminders, sorted by due date, from one list or all. By default only incomplete ones. Dates are ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. A date-only 'due_end' includes that whole day. Reminders without a due date are left out when a due range is given.

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": "list_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoList name or id. Names ignore case. Default: all lists.
limitNoMost results to return. Default 50, maximum 500.
filterNoWhich reminders to show. Default incomplete.
due_endNoOnly reminders due before this. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
due_startNoOnly reminders due at or after this. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: results are sorted by due date, defaults to incomplete only, and reminders without a due date are dropped when a due range is supplied — a non-obvious filtering side effect.

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?

Five short sentences, front-loaded with the core purpose, then defaults, then date-format and edge-case semantics. Every sentence carries information; no filler or restatement of the title.

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 list tool with a fully documented schema and no output schema, the description covers purpose, defaults, ordering, and the key date-filtering edge case. Return shape and pagination are left implicit, which is acceptable for a simple listing operation but is the one remaining gap.

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 the schema already documents all five parameters, and the baseline is 3. The description adds some meaning, notably that a date-only due_end covers the whole day and that undated reminders are excluded under a due range, but it does not touch the list, limit, or filter parameters beyond what the schema says.

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 and resource ('List reminders'), plus the ordering ('sorted by due date') and scope ('from one list or all'), which lets an agent distinguish it from generic enumeration. It does not explicitly contrast with the sibling search_reminders, so it stops short of full differentiation.

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?

The description explains defaults ('By default only incomplete ones') and the due-range filtering behavior, which implies when the tool fits. However, it never names an alternative such as search_reminders or states when not to use this tool, leaving comparison to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.