Skip to main content
Glama
contextstream

ContextStream MCP Server

Reminder

reminder
Read-onlyIdempotent

Create, list, and manage alerts with priority and recurrence. Snooze, complete, or dismiss as needed.

Instructions

Reminder management. Actions: list, active (pending/overdue), create, snooze, complete, dismiss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
workspace_idNoWorkspace ID (UUID).
project_idNoProject ID (UUID).
reminder_idNoReminder ID (UUID).
titleNoShort descriptive title.
contentNoFull content/body.
remind_atNoISO 8601 datetime
priorityNoPriority level.
recurrenceNoRecurrence pattern (daily, weekly, monthly).
keywordsNoKeywords for matching.
untilNoISO 8601 datetime
statusNoInput parameter: status.
contextNoContext to match relevant reminders.
limitNoMaximum number of results to return.
Behavior1/5

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

Description includes mutation actions like 'create' and 'complete', contradicting the readOnlyHint annotation set to true; no additional behavioral traits disclosed.

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

Conciseness3/5

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

Extremely concise (one sentence), but lacks essential details such as action-parameter relationships, making it insufficiently informative.

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

Completeness1/5

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

With 14 parameters, six actions, no output schema, and no guidance, the description is woefully incomplete for an agent to invoke the tool correctly.

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 covers all parameters with descriptions, but the tool's description adds no extra meaning or contextual grouping, so baseline score 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?

The description clearly states it manages reminders and lists specific actions, but does not differentiate between the tools' purpose from siblings beyond the name.

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 guidance on when to use each action or how to choose between this tool and alternatives; the description merely enumerates actions without context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/contextstream/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server