Skip to main content
Glama

Coline

Set event reminders

set_event_reminders
DestructiveIdempotent

Replaces the person's own reminders for an event: how long before, and where (in Coline, desktop, phone).

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": {
      "workspace": "<workspace>",
      "eventId": "<eventId>",
      "reminders": "<reminders>"
    },
    "name": "set_event_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
remindersYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description earns credit by explaining what that destruction means (the whole reminder set is replaced) and by scoping it to 'the person's own reminders,' implying others' reminders are untouched. It still doesn't say what an empty list does or whether ownership permission is required.

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 front-loaded sentence whose clause structure maps directly onto the tool's semantics: replace scope first, then the two value dimensions. No filler.

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?

With an output schema present and only three parameters, the description covers the mutation semantics and the otherwise-undocumented nested parameters. The main residual gap, clearing all reminders via an empty array, is edge-case detail rather than something needed to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the nested reminders items have no schema descriptions at all, so the description does real work by glossing minutesBefore as 'how long before' and deliveryChannels as 'where (in Coline, desktop, phone).' It does not cover the bounds (max 10 reminders, 525600 minutes) or the empty-list case, but those exist in the schema.

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: 'Replaces the person's own reminders for an event,' plus the two dimensions being set (timing and delivery location). It clearly distinguishes a write/set operation from the read-side sibling get_event_reminders, but never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Replaces' implies a full overwrite, which is real implicit guidance (you must supply the complete desired set, not an incremental add). However, there is no explicit statement of when to use this versus get_event_reminders or update_event, and no mention of prerequisites such as being the event owner.

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.

Resources