Skip to main content
Glama

List reminders

list_reminders
Read-only

List the guide's reminders, active or completed.

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
limitNo
offsetNo
statusNo
booking_idNo
activity_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the status vocabulary already encoded in the enum and does not describe ordering, default page size, total counts, or what an empty result means. For a six-parameter list tool this leaves the behavioral picture thin.

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?

A single short sentence with the resource scoping front-loaded and no filler. It is efficient, though the brevity comes at the cost of detail rather than being tight while complete.

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?

With six optional parameters, 17% schema coverage, no output schema and no annotation on return shape, the description should explain pagination, default status behavior and result contents. It does none of these, so an agent cannot predict what a call returns or how to page through reminders.

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 only 17%, with business_id the sole documented parameter; limit, offset, status, booking_id and activity_id carry no schema descriptions. The description's "active or completed" corroborates the status enum but adds no format, default, or interaction detail, and it says nothing to compensate for the undocumented filters or pagination parameters.

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 (List) and resource (the guide's reminders) and indicates the scope covers both active and completed items. It is clear enough to distinguish from action siblings like complete_reminder or delete_reminder, though the possessive "guide's" leaves the ownership scoping slightly ambiguous since no guide_id parameter exists.

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 description mentions "active or completed" but never states when to choose this tool over alternatives, nor how to use the status parameter to narrow results. There is no guidance on pagination or on when filtering by booking_id or activity_id would be appropriate.

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