Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calendar_create_event

Create a new event in the connected calendar (Google or Outlook). Specify the title, start time, end time, and optionally invite attendees. Use ISO 8601 format for dates (e.g., 2024-12-15T14:00:00).

Input Schema

NameRequiredDescriptionDefault
endNoEvent end time in ISO 8601 format. If not provided, defaults to 1 hour after start. Also accepts 'end_time' as alias.
startNoEvent start time in ISO 8601 format (e.g., 2024-12-15T14:00:00). Also accepts 'start_time' as alias.
titleNoAlias for summary - event title.
summaryNoEvent title/summary. Required. Also accepts 'title' as alias.
end_timeNoAlias for end - event end time.
locationNoEvent location (physical address or virtual meeting link).
timezoneNoIANA timezone (e.g. 'Asia/Bishkek') that start/end WITHOUT an offset are in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone, which is what an event with no timezone gets.
attendeesNoList of attendee email addresses to invite.
account_idNoCalendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.
start_timeNoAlias for start - event start time in ISO 8601 format.
calendar_idNoCalendar ID to create the event in. OMIT to use the agent's configured default calendar (or primary).
descriptionNoEvent description/notes.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
add_google_meetNoOld name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting.
conference_dataNoConference data for Google Meet. Alternative to add_google_meet flag.
add_online_meetingNoIf true, the event gets a video meeting link of its own: Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar. OMIT to skip the link.
send_notificationsNoWhether to email the attendees about the new event. true (default) sends the invitations; false saves the event silently. On Outlook calendars a silent save is refused when the event has guests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / send_notifications
      Added value: +{
+  "default": true,
+  "description": "Whether to email the attendees about the new event. true (default) sends the invitations; false saves the event silently. On Outlook calendars a silent save is refused when the event has guests.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.",
+  "type": "integer"
+}
    • changedInput schema / properties / add_google_meet / description
      Previous value: -"If true, automatically creates a Google Meet link for the event. OMIT to skip Meet link."New value: +"Old name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting."
    • addedInput schema / properties / add_online_meeting
      Added value: +{
+  "description": "If true, the event gets a video meeting link of its own: Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar. OMIT to skip the link.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone for the event (e.g., 'America/New_York', 'UTC')."New value: +"IANA timezone (e.g. 'Asia/Bishkek') that start/end WITHOUT an offset are in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone, which is what an event with no timezone gets."
  4. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  5. Added
  6. Removed
  7. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID to create event in. Defaults to primary calendar."New value: +"Calendar ID to create the event in. OMIT to use the agent's configured default calendar (or primary)."
  8. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that attendees can optionally be invited and the ISO 8601 convention, but says nothing about notification behavior, conferencing, alias handling, timezone resolution, or what the response contains.

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?

Two sentences, front-loaded with the action and followed by the required inputs and format rule. No filler, though 'Specify the title, start time, end time' restates schema content and could have been spent on the riskier parameters.

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 17-parameter creation tool with a nested conference_data object and no output schema, the description covers only the minimal happy path. It omits anything about calendar selection, online meeting generation, notification side effects, or what an event created returns, leaving the agent to reconstruct that from the schema alone.

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?

With 17 parameters the schema does the heavy lifting, but the description correctly foregrounds the four core inputs (title, start, end, attendees) and states the date format expectation, which is genuine navigational value beyond a flat parameter list. It still says nothing about timezone, calendar_id, account_id, send_notifications or the legacy aliases, so it stays near the schema baseline rather than exceeding it.

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?

'Create a new event in the connected calendar (Google or Outlook)' states a specific verb and resource and names the calendar backends, which separates it cleanly from calendar_update_event, calendar_list_events and calendar_delete_event. It stops short of explicitly routing to those siblings, so it is clear but not maximally differentiated.

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 description implies the intended use (creating events) and gives a date-format convention, but never states when to prefer alternatives such as calendar_check_availability first or calendar_update_event for changes. Usage is inferable rather than guided.

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

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