Skip to main content
Glama

list_reminders

Read-onlyIdempotent

Retrieve persisted Hub reminders to review upcoming tasks or overdue items without modifying them. Filter for due-only reminders at session start to see what needs attention now.

Instructions

List persisted Hub reminders without changing them.

    Prefer due_only=true at session start to surface only reminders that need
    attention now. Set include_handled=true only when historical handled
    reminders are relevant.
    

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
due_onlyNoDefaults to false. True returns currently due, unhandled reminders using their schedule and ignores include_handled.
include_handledNoDefaults to false. True includes handled reminders only when due_only=false.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.22.0
    • addedInput schema / properties / due_only / description
      Added value: +"Defaults to false. True returns currently due, unhandled reminders using their schedule and ignores include_handled."
    • addedInput schema / properties / include_handled / description
      Added value: +"Defaults to false. True includes handled reminders only when due_only=false."
  2. First observedv0.12.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description reinforces this with "without changing them" and "persisted," but adds no further behavioral detail such as ordering, volume, or pagination. With annotations carrying the safety burden, a 3 is appropriate.

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?

Three short sentences, no filler, with the read-only scope stated first and the parameter recommendations following. Every sentence carries actionable information.

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?

This is a simple two-boolean read tool with an output schema and full annotation coverage, and the description covers scope and parameter intent adequately. Nothing an agent needs in order to call it correctly is missing, though it says nothing about the shape or size of the result set.

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 both booleans and their defaults are already documented in the schema, including that due_only ignores include_handled. The description adds only a recommended default context ("at session start"), which is meaningful but narrow. Baseline 3 holds since the schema does the heavy lifting.

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?

The description states a specific verb and resource ("List persisted Hub reminders") and adds a scope boundary ("without changing them"), which implicitly separates it from the mutating sibling set_reminder. It never names a sibling explicitly, so an agent must infer the read-vs-write split from wording alone.

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?

It gives concrete situational guidance: prefer due_only=true at session start, and set include_handled=true only when historical records matter. This is clear when-to-use advice, though it is framed around parameter presets rather than alternative tools.

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