Skip to main content
Glama

List my reminders to my human

reminder_list
Read-only

List your reminders to your human: status (active, paused or parked), next_run_at, the last result (sent, or why not) and owner_email: whether email reaches them now. Works after the plan ended. Find the reminder_id for reminder_update or reminder_delete here; wake-ups to yourself: schedule_list.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "orm_exampleexampleexample2"
    },
    "name": "reminder_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "orm_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.3/5.0
Behavior4/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 safety is covered. The description adds value beyond them by disclosing the shape of the returned records — status enum, next_run_at, the last result including "why not" on failure, and whether owner_email actually reaches the human — plus the post-plan persistence trait. It does not mention pagination or result volume, which keeps it short of a 5.

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 returned fields are front-loaded and every clause carries information — no filler sentences. The colon-chained phrasing ("owner_email: whether email reaches them now") and the compressed "wake-ups to yourself: schedule_list" fragment are dense enough to slow parsing slightly, costing a point.

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?

With no output schema, the description carries the return-value burden itself, and it does so by naming the fields the agent will receive. Combined with read-only annotations and full schema coverage, an agent has enough to call it correctly; only paging/limits are unaddressed.

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 (instance_id, passport_token) are already documented in the schema and the baseline is 3. The description adds no extra meaning about instance_id provenance or when the passport_token fallback is appropriate, so it neither compensates nor detracts.

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 opens with a specific verb and resource ("List your reminders to your human") and then enumerates exactly what each entry exposes: status values (active, paused, parked), next_run_at, last result, and owner_email. It explicitly distinguishes itself from reminder_update/reminder_delete (which consume the reminder_id found here) and from schedule_list (self wake-ups), so an agent can separate it from siblings without opening any schema.

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 states the concrete downstream use ("Find the reminder_id for reminder_update or reminder_delete here") and redirects the adjacent-but-different case to a named alternative ("wake-ups to yourself: schedule_list"). It also flags the persistence condition "Works after the plan ended," which tells the agent this listing remains valid outside an active plan.

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.