Skip to main content
Glama

mu

by mu.micro
OverviewDiscussionsAdmin

Create events

events_create

Schedule a reminder or event at a given time; optionally repeating, and optionally running a prompt through the agent when it fires

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional extra detail
whenYesWhen to fire, RFC3339 with timezone offset, e.g. 2026-07-22T15:00:00+01:00
titleYesWhat to be reminded about, e.g. 'Call the dentist'
promptNoOptional instruction to run through the agent when it fires, e.g. "brief me on today's news". The answer is mailed to you
repeatNoHow often it recurs: hourly, daily, weekly or monthly. Omit for once
advanceNoOptional advance trigger: minutes before the event and recipient user or agent. Agent prepares a read-only report for delivery at when; actions that change records must use a normal scheduled prompt without advance
minutesNoHow long it lasts in minutes (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / advance
      Added value: +{
+  "description": "Optional advance trigger: minutes before the event and recipient user or agent. Agent prepares a read-only report for delivery at when; actions that change records must use a normal scheduled prompt without advance",
+  "type": "object"
+}
  2. Added
  3. Removed
  4. Changed4 schema fields changed
    • changedInput schema / properties / minutes / description
      Previous value: -"How long it lasts in minutes (default 30). What events_free subtracts."New value: +"How long it lasts in minutes (default 30)"
    • changedInput schema / properties / prompt / description
      Previous value: -"Optional instruction to run through the agent when it fires, e.g. \"brief me on today's news\". The answer is mailed to you. This is how you set up something recurring like a morning briefing."New value: +"Optional instruction to run through the agent when it fires, e.g. \"brief me on today's news\". The answer is mailed to you"
    • changedInput schema / properties / repeat / description
      Previous value: -"How often it recurs: hourly, daily, weekly or monthly. Omit for once."New value: +"How often it recurs: hourly, daily, weekly or monthly. Omit for once"
    • changedInput schema / properties / title / description
      Previous value: -"What to be reminded about"New value: +"What to be reminded about, e.g. 'Call the dentist'"
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full burden. It discloses that the event may repeat and that a prompt will be run through the agent with the answer mailed to the user, which is genuinely useful behavioral context, but says nothing about permissions, side effects, failure behavior, or whether the created event can later be edited or freed.

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

Conciseness4/5

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

A single, tightly packed sentence that front-loads the core action and appends the two optional behaviors. No filler, though the semicolon clauses are dense enough that a little structuring could aid scanning.

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?

For a 7-parameter mutation tool with a nested object, no annotations, and no output schema, the description covers the headline behaviors but omits what is returned (e.g., event id), permission requirements, and interaction with sibling lifecycle tools, leaving real gaps.

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 every parameter (including the nested advance object with its read-only-report constraint) is already documented. The description adds no syntax, defaults, or format detail beyond what the schema provides; baseline 3 is appropriate.

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+resource (schedule a reminder or event) and names the two distinguishing capabilities: optional recurrence and an optional agent prompt fired at trigger time. This separates it from events_list, events_update, and events_delete, though it never names a sibling 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?

Usage is implied by the described capabilities (use it to create a one-shot or repeating reminder, or a prompt-driven automation), but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as tasks_create or events_update for modifying existing events.

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

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