Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_reminder_remove

Remove event reminders by reminder ID, minutes-before timing, or all at once, and return what remains so users can update calendar notifications.

Instructions

Remove reminders from an event (by minutes, by reminder_id, or all). Returns what is left.

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": {
      "event_id": "<event_id>"
    },
    "name": "calendar_reminder_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoRemove every reminder of the event.
minutesNoRemove the reminder(s) set this many minutes before.
event_idYesEvent id.
reminder_idNoRemove this reminder (reminder_id from calendar.get).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add one genuinely useful fact — 'Returns what is left' — which covers the absent output schema. But it omits mutation-relevant traits: whether removal is reversible, whether minutes-matching deletes all matching reminders, and what happens if nothing matches.

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?

Two sentences, zero filler, with the selection modes front-loaded and the return behavior trailing. Nothing could be cut without losing information.

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?

For a 4-parameter mutation with full schema coverage and no output schema, the description plus schema is nearly sufficient — the return note fills the output-schema gap. The only shortfall is missing guidance on parameter interaction and non-matching-reminder behavior.

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% and each parameter is already documented, including the useful hint that reminder_id comes from calendar.get. The description's mode list restates the schema rather than adding new meaning, so baseline 3 applies; it gives no guidance on mutual exclusion among all/minutes/reminder_id.

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?

Specific verb (remove) plus resource (reminders from an event) and the three selection modes, which cleanly separates it from the sibling calendar_reminder_add. It never names the sibling explicitly, but the add/remove pairing is unambiguous.

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?

The parenthetical lists the three removal modes, implying when each applies, but the description never states when the agent should reach for this tool versus calendar_update (which may also alter reminder state) or when removal is inappropriate. Usage is inferable rather than stated.

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

Deploy Server

Other Tools