workbench MCP server

Overview Schema Source Related Servers Discussions Admin

create_event

Create calendar events with automatic conflict detection; if a slot is taken, returns conflicting events so you can retry or override.

Instructions

Create a calendar event.

    Refuses to double-book by default: if the slot overlaps an existing
    event the call fails and returns the conflicts, so you can pick another
    time (see find_free_slot) or retry with allow_conflict=true.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	Yes	End time, e.g. 2026-09-15T14:30:00.
`notes`	No	Agenda or context.
`start`	Yes	Start time, e.g. 2026-09-15T14:00:00.
`title`	Yes	Short meeting title.
`location`	No	Room name or meeting link.
`attendees`	No	Comma-separated email addresses.
`allow_conflict`	No	Set true to book on top of an existing event.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does it well. It discloses that double-booking is refused by default, that failures return the conflicts, and that allow_conflict overrides this behavior—details not visible in the schema's static defaults.

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

Conciseness5/5

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

The description is compact: one clear purpose statement followed by a focused behavioral note. Every sentence earns its place, and the primary purpose is front-loaded.

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

Completeness5/5

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

For a create operation with an output schema and no nested objects, this description captures the key non-obvious behavior (conflict refusal) and the way to bypass it. The return format is covered by the output schema, so nothing critical is missing.

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?

Schema coverage is 100%, so the baseline is already met. The description adds situational meaning for allow_conflict by framing it as a retry mechanism after a conflict, and it points to find_free_slot for alternative time selection, which is extra context beyond the schema.

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 opens with 'Create a calendar event,' a specific verb and resource that clearly distinguishes this from siblings like list_events, delete_event, and create_issue. The follow-up about conflict behavior reinforces its role as the write path for calendar entries.

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

Usage Guidelines4/5

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

The description gives concrete, actionable guidance for the overlapping-slot case: if the call fails due to a conflict, the agent can use find_free_slot to pick another time or retry with allow_conflict=true. It doesn't explicitly rule out other sibling tools, but the context is clear enough for typical use.

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

Deploy Server