Skip to main content
Glama

search_reminders

Read-only

Find reminders across all lists by case-insensitive text in titles or notes, including completed and incomplete items.

Instructions

Find reminders whose title or notes contain the query (ignores case), in all lists, complete and incomplete.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return. Default 50, maximum 500.
queryYesText to look for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile. The description adds useful behavioral detail by explaining that matching is case-insensitive, applies to title and notes, and spans all lists and completion states.

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?

The description is a single well-formed sentence with the search semantics front-loaded and no redundant wording. Every clause contributes useful matching or scope information.

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

Completeness5/5

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

For a simple two-parameter search tool with annotations and complete schema descriptions, the definition covers the necessary behavior: matching fields, case behavior, and scope across lists and completion status. No output schema exists, but the return concept is implicit in 'Find reminders.'

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 schema already documents both parameters. The description adds meaning beyond the schema by clarifying that the query matches reminder title or notes and ignores case; the limit parameter remains fully documented in 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?

The description uses a specific verb ('Find') and resource ('reminders'), and states the matching fields ('title or notes'), case behavior, and scope ('all lists, complete and incomplete'). This clearly distinguishes it from list_reminders and other search_* siblings.

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 implied by 'Find reminders whose title or notes contain the query,' but the description does not explicitly say when to use this instead of list_reminders or when not to use it. No alternatives or exclusions are named.

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