Skip to main content
Glama

Coline

Create event

create_event
Destructive

Schedules a meeting or blocks time on the person's calendar, shown to them on their week. Pass an IANA time zone. Not idempotent: after a timeout, check list_events before trying again.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "title": "<title>",
      "start": "<start>",
      "end": "<end>",
      "timeZone": "<timeZone>"
    },
    "name": "create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
kindNo
colorNo
linksNoFiles, channels or web pages to attach.
startYesISO 8601 with a time zone offset, e.g. 2026-11-20T15:00:00-08:00.
titleYes
allDayNo
locationNo
timeZoneYesIANA time zone, e.g. America/Vancouver.
attendeesNoEmail addresses. Teammates are added directly; anyone else gets an email invite once the person approves it.
videoCallNoAdd a Coline meeting link.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
calendarIdNoCalendar to put it on; default the person's own.
visibilityNo
callJoinUrlNoA video call link from elsewhere.
descriptionNo
callProviderNo
transparencyNofree: doesn't block the person's time.
guestAttendeesNoPeople outside Coline, with a name and time zone.
recurrenceRuleNoHow it repeats; {} or null stops it repeating.
attendeeUserIdsNoTeammates by user id, instead of attendees by email.
meetingSettingsNo
reminderMinutesNoRemind the person this many minutes before.
travelMinutesAfterNo
travelMinutesBeforeNo

Output Schema

NameRequiredDescriptionDefault
eventYes
invitesYesWhether emails to people outside Coline went out, or wait for the person's approval in Coline.
approvalUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=true and openWorldHint=true. The description reinforces non-idempotency with a specific recovery workflow (list_events), which adds operational value beyond the boolean, but it never explains what makes this destructive or open-world – i.e., that external attendees receive an email invite that requires the person's approval, a detail buried only in the schema.

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?

Three short sentences, front-loaded with purpose, then the non-obvious input requirement, then the failure-handling rule. Little waste, though 'shown to them on their week' is slightly cryptic and no sentence addresses the tool's substantial side effects.

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?

An output schema exists, so return values need not be explained, and the retry caveat is a good addition. But for a 25-parameter mutation tool that sends external invites and creates recurring events, the description leaves major behavioral consequences and most optional-field choices undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 25 parameters and only 56% schema description coverage, the description must compensate and does not. Its single parameter remark, 'Pass an IANA time zone,' simply restates the required timeZone field that the schema already documents with an example, while attendees vs. attendeeUserIds vs. guestAttendees, recurrenceRule, transparency, and callJoinUrl go unaddressed in the description.

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?

The description opens with a concrete verb and resource: scheduling a meeting or blocking time on the calendar, and notes where it appears ('their week'). It is clearly a creation tool, but it never distinguishes itself from create_event_template or says when to use this versus create_event_template.

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?

There is no explicit when-to-use / when-not statement, nor a pointer to update_event or create_event_template as alternatives. The one piece of usage guidance is a recovery rule: after a timeout, check list_events before retrying, which is genuinely actionable but covers only failure handling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources