Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

List a thread's reminders

list_reminders
Read-onlyIdempotent

List the person's reminders in one Thread: its general reminder and those on its Notes, each with note_id (null for the general one), rule, next_at, whether it is due, and set_by (a connection's id when an assistant set it). get_reminder reads one; set_reminder and remove_reminder change them.

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": "list_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/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 behavior, so the safety profile is covered. The description adds genuine value by enumerating the returned fields, including the subtle note_id=null case for the thread-level reminder and the meaning of set_by when an assistant set it. It omits ordering and pagination behavior, which keeps it from 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 scope statement is front-loaded and every clause about returned fields carries information an agent needs. The dense run-on enumeration of fields is functional but slightly less scannable than separate sentences would be.

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 one-parameter read-only tool with no output schema, the description supplies exactly the missing piece: what each returned field means, including the null note_id and set_by provenance. Nothing an agent needs in order to call or interpret this tool is absent.

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?

There is a single parameter, thread_id, and schema coverage is 100% with a description pointing at how to obtain one (list_threads, search, or a read). The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

States a specific verb and resource with explicit scope: 'List the person's reminders in one Thread: its general reminder and those on its Notes'. It also contrasts with 'get_reminder reads one', so an agent can distinguish listing from fetching a single reminder 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 Guidelines4/5

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

Names the sibling alternatives explicitly (get_reminder for one, set_reminder/remove_reminder for changes), which gives clear routing context. It stops short of stating exclusions or prerequisites, so it is clear but not a full when/when-not guide.

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