Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Read a reminder

get_reminder
Read-onlyIdempotent

Read the person's reminder on a Thread (its general one: omit note_id) or on one Note in it, or null when there is none: its rule, next_at, due, snooze_at and set_by (a connection's id when an assistant set it). It is theirs alone: nobody else sees it, and it has no text. Check it before set_reminder; list_reminders gives all of a Thread's at once.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
note_idNoA Note's id for its own reminder; omit for the Thread's general reminder. A live Note out of Trash, wherever it moved, in such a Thread.
thread_idYesA Thread you can read (list_threads, search or a read).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: it returns null when no reminder exists, it enumerates the returned fields (rule, next_at, due, snooze_at, set_by) in the absence of an output schema, and it flags that the reminder is private and has no text — a non-obvious detail that prevents an agent hunting for note content in the response.

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 core operation and its two modes are front-loaded, and the routing sentence to set_reminder/list_reminders comes last where it belongs. The phrasing is dense and slightly awkward in places (the 'or null when there is none:' colon construction), and the privacy sentence borders on redundant, but no sentence is wasted.

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 only two parameters, annotations covering safety and no output schema, the description carries the return-shape burden itself and does so by listing the fields and the null case. It stops short of describing failure behavior for unreadable or trashed Threads, which the schema alludes to, but for a simple lookup this is close to complete.

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 coverage is 100% and both parameters are described there, including the note_id omission rule and the Thread requirement. The description restates the omit-note_id convention rather than adding new syntax or constraints, so the baseline of 3 applies. The parenthetical about set_by being a connection's id is return-value context, not parameter meaning.

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 names a specific verb (read) and resource (a reminder), and explicitly scopes the two variants: a Thread's general reminder when note_id is omitted, or one Note's reminder otherwise. It also names the sibling that does the bulk version (list_reminders), so an agent can separate it from neighbouring read tools without opening a 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 precondition to act ('Check it before set_reminder') and points to the alternative for the aggregate case ('list_reminders gives all of a Thread's at once'). That is explicit when-to-use plus a named alternative, which is the top of this scale.

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

All ThreadPage 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