Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

reminder_list

Read-onlyIdempotent

List your active reminders (both one-time and recurring).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20)
agent_idNoOnly this agent's reminders. Leave it out to list the whole workspace's; each row then names the agent it belongs to. Ignored in agentic mode.
thread_idNoFilter by thread
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
include_firedNoInclude already-fired one-time reminders (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Agent ID (required when calling from MCP; ignored in agentic mode)."New value: +"Only this agent's reminders. Leave it out to list the whole workspace's; each row then names the agent it belongs to. Ignored in agentic mode."
  3. Added
  4. Removed
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds the useful scope detail that only 'active' reminders are returned and that both one-time and recurring types are included, which aligns with the include_fired default of false. It stops short of describing pagination or the returned row shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the key scope qualifier ('active') is front-loaded. Nothing could be trimmed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a read-only list tool whose annotations cover the safety profile and whose schema covers all parameters, but with no output schema the description could have sketched what a returned row contains (e.g. the owning agent) or the default exclusion of fired 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 100%, so all five parameters are already documented in the schema, including agent_id scoping and include_fired. The description only loosely gestures at one of them ('one-time and recurring'), adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List your active reminders') and scopes it with 'active' plus 'both one-time and recurring'. It does not explicitly distinguish itself from siblings reminder_set and reminder_cancel, but the read/list nature is unmistakable.

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?

No when-to-use or when-not-to-use guidance, and no mention of the sibling tools for creating or cancelling reminders. The agent must infer that this is the retrieval counterpart to reminder_set/reminder_cancel.

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

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