Skip to main content
Glama
garoon
by garoon

Create Schedule Event

garoon-create-schedule-event

Create a schedule event in Garoon by providing subject, start and end times, event type, attendees, and facilities. Supports both regular and all-day events.

Instructions

Create a new schedule event in Garoon

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd datetime of the event - REQUIRED when isStartOnly=false, OPTIONAL when isStartOnly=true. For ALL_DAY events, endDateTime is always required
notesNoNotes/description of the schedule event
startYesStart datetime of the event - ALWAYS REQUIRED for both REGULAR and ALL_DAY events
subjectNoSubject/title of schedule eventNew Schedule
isAllDayNoOnly applies to REGULAR events. When true, the event spans the entire day but still requires specific start/end times (start-00:00, end-23:59). This is different from ALL_DAY event type which doesn't require time specifications.
watchersNoList of watchers for the schedule event
attendeesNoList of attendees for the schedule event
eventMenuNoThe event label (e.g., 'Meeting', 'Holiday', etc.)
eventTypeNoEvent type that determines validation rules: 'REGULAR' = event with specific start/end times (can be modified by isAllDay flag start-00:00, end-23:59), 'ALL_DAY' = event spanning full days without time specifications (only date matters)REGULAR
facilitiesNoList of facilities for the schedule event
isStartOnlyNoWhen true, the event only has a start time (no end time). When false, both start and end times are required. This field controls whether the 'end' parameter is mandatory.
visibilityTypeNoPublishing type { 'PUBLIC': 'Public', 'PRIVATE': 'Private' }PUBLIC
facilityUsingPurposeNoFacility usage purpose - required if 'Application for facility use' is enabled

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message. Present on error
resultNoResult of the operation. Present on success
statusNoHTTP status code from the Garoon API. Present only when the error is an HTTP error response
responseTextNoRaw response body from the Garoon API. Present only when the error is an HTTP error response
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It only states 'Create a new schedule event' with no information about authentication requirements, side effects, error conditions, or what happens on success. This is insufficient for a mutation tool with complex parameters.

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?

The description is a single sentence with no extraneous words. However, it is possibly too concise, missing crucial context that could help the agent. Nonetheless, it is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (13 parameters, nested objects, output schema), the one-line description is inadequate. It does not cover error scenarios, prerequisites, or the implications of setting various parameters, despite the rich input schema.

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 the baseline is 3. The description adds no additional parameter meaning beyond the schema's own detailed descriptions, which are comprehensive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'new schedule event in Garoon', making the tool's purpose unambiguous. It distinguishes from sibling tools, which are mostly read-only or search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidelines are provided on when to use this tool versus alternatives. For instance, it does not mention when to use garoon-get-schedule-events or garoon-search-available-times instead. The description lacks context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/garoon/garoon-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server