Skip to main content
Glama

Reminders List

reminders_list

List reminders from macOS, optionally filtered to a specific list and with a configurable limit.

Instructions

Open reminders, optionally in one list.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
list_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not state that this is a read-only operation, whether authentication is required, how pagination or the default limit behaves, or what the response contains. It only hints that results can be scoped to one list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single sentence and is front-loaded, but its brevity comes at the cost of clarity. The wording is efficient but under-specified, especially around the meaning of "Open" and the limit parameter.

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

Completeness2/5

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

This is a simple two-parameter tool with no output schema and no annotations, so the description should explain the filter semantics and pagination behavior. It omits the limit parameter entirely and leaves "Open" undefined, making it insufficiently complete for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to compensate. It partially explains list_id by saying results can be limited to "one list," but it does not explain the limit parameter, its default of 50, or what value shape list_id expects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description implies retrieving open reminders and optionally scoping to a single list, which goes slightly beyond the title. However, "Open reminders" is ambiguous: "Open" could describe reminder status or an action, and the description never clearly says this is a listing/retrieval operation.

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

Usage Guidelines2/5

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

The phrase "optionally in one list" gives minimal filtering context, but there is no explicit guidance on when to use this tool versus siblings, no prerequisites, and no exclusions. The agent must infer the tool's role from its name alone.

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