Skip to main content
Glama

Export calendar reminders

export_reminders

Create an .ics calendar file containing weekly reviews, monthly habit-strength checks, and quarterly reviews, then return its path for calendar import so reminders work without a server.

Instructions

Writes a calendar file (.ics) with the weekly review, the monthly habit-strength check and the quarterly review, so reminders work without any server. Returns the file path to import into a calendar app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo18:00
weekdayNoSU

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key traits: this is a write operation that creates a file, it requires no server, and it returns a file path. It omits where the file is written, whether an existing file is overwritten, and whether the reminders are one-off or recurring, which are material for a file-writing tool.

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, no filler. The producing action and the artifact come first, and the return value is stated last where an agent will look for it. Nothing repeats the name or title.

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?

No output schema exists, so the description correctly states the return value (file path) and its intended use. Candidate weaknesses are the unmentioned time/weekday parameters and the unspecified file destination, but otherwise the definition covers what an agent needs to invoke this tool on defaults and use the result.

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?

Two parameters at 0% schema description coverage means the description must explain them, and it explains neither. 'time' (default 18:00, HH:MM pattern) and 'weekday' (enum, default SU) are clearly the reminder scheduling controls, but the description never says so, leaving the agent to infer their role from the schema alone.

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?

Names a concrete verb and artifact: 'Writes a calendar file (.ics)' and enumerates the three reminders it contains (weekly review, monthly habit-strength check, quarterly review). An agent knows exactly what the tool produces. It does not contrast itself with any sibling (e.g. weekly_review, monthly_check, quarterly_review), so a 4 rather than a 5.

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 clause 'so reminders work without any server' implies the use case is offline/standalone reminder generation, and 'the file path to import into a calendar app' implies the follow-up step. There is no explicit when-to-use vs. when-not, and no statement about whether this should be called instead of, or alongside, the individual review tools.

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