Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

calendar_create_event

Create a new event in Google Calendar. 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

TableJSON 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).
timezoneNoTimezone for the event (e.g., 'America/New_York', 'UTC').
attendeesNoList of attendee email addresses to invite.
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_meetNoIf true, automatically creates a Google Meet link for the event. OMIT to skip Meet link.
conference_dataNoConference data for Google Meet. Alternative to add_google_meet flag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Added
  3. Removed
  4. 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)."
  5. 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 non-read-only, non-destructive, non-idempotent, open-world behavior, so the safety profile is covered. The description adds only the ISO 8601 input convention; it never says whether invitees actually receive notifications, whether the event is immediately live on shared calendars, or what side effects creation has.

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 tight sentences, purpose front-loaded, followed by the required inputs and one concrete format example. No filler; it could be stronger only by ordering inputs to match required vs optional usage.

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?

With 14 mostly aliased parameters, nested conference_data, no output schema, and full annotation coverage, the description covers the core invocation path adequately. It omits what the call returns (created event identifier/link) and does not reconcile the stated 'required' title with an empty required list, a minor gap.

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 coverage is 100%, so every parameter including the alias fields (title/summary, start/start_time, end/end_time, calendar_id, add_google_meet) is already documented. The description restates title/start/end and an ISO 8601 example but adds no meaning beyond the schema, so the baseline 3 applies.

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?

Explicit verb+resource: 'Create a new event in Google Calendar.' The create verb cleanly separates it from calendar_update_event, calendar_delete_event, and calendar_list_events. It does not, however, name any sibling or scope constraints 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 only implied through the field checklist ('Specify the title, start time, end time, and optionally invite attendees') and format guidance. There is no statement of when to use this instead of calendar_update_event or calendar_check_availability, and no prerequisites are given.

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