Skip to main content
Glama
Sign In

Flash

by com.flashmemorize
OverviewDiscussionsAdmin

Study panel: remind me

panel_reminders

Used by Flash's study panel only; never call it yourself. Turns on reminders when cards are due, at this time of day, after the user tapped the panel's offer; with decline, stops the offer after the user tapped Not now.

Input Schema

NameRequiredDescriptionDefault
declineNoThe user tapped Not now: no reminders, and the offer stops.
timezoneNoThe browser's IANA time zone, e.g. `America/New_York`.

Output Schema

NameRequiredDescriptionDefault
onYesWhether reminders are on now.
messageNoWhat was set up, for the person to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / decline
      Added value: +{
+  "default": false,
+  "description": "The user tapped Not now: no reminders, and the offer stops.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only but non-destructive operation, and the description adds useful behavioral context: it is triggered only by a user tapping the panel's offer or Not now. It does not elaborate on persistence or side effects beyond enabling reminders or stopping the offer, but that is reasonable given the annotation coverage.

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?

The description is two compact sentences with the critical restriction front-loaded. The phrasing 'when cards are due, at this time of day, after the user tapped...' is slightly dense, but it wastes little space and keeps the key gating condition visible.

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?

Because an output schema exists, the description does not need to explain return values. For a panel-only internal tool, it provides enough context to keep an agent from misusing it and to understand the user-triggered flow, though the exact meaning of 'this time of day' could be clearer.

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 parameters are already documented in the schema. The description reinforces the decline behavior ('stops the offer after the user tapped Not now') but does not add substantial new semantics beyond what the schema provides for timezone or decline.

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 action (turning reminders on or stopping the offer) and resource context (study panel reminders), so an agent can understand what the tool does. It is clearly separated from most siblings by the 'study panel only' framing, though the mechanics of the reminder itself remain slightly vague.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ('after the user tapped the panel's offer') and when-not-to-use guidance ('never call it yourself'). It also distinguishes the decline path ('after the user tapped Not now'), leaving little ambiguity about invocation conditions.

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

All Flash toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources