Skip to main content
Glama

Create calendar event

event_create

Create a calendar event. Defaults to draft. Status published shows it on Your page right away: ask the person first and pass confirm_publish: true. Use an IANA timezone and ISO dates with offsets. Requires API key scope: draft.

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": {
      "event": "<event>"
    },
    "name": "event_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYes
confirm_publishNotrue only after the person explicitly approved publishing; required whenever this call publishes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the non-read-only, non-destructive, non-idempotent profile; the description adds the consequential behavior that a "published" status makes the event visible on the person's page immediately and demands explicit human approval. It also discloses the auth/scope requirement (API key scope: draft). It stops short of describing the returned object, which matters for a non-idempotent create.

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?

Four short sentences, each carrying distinct information: action, default state, publish caveat, formatting rules, and auth scope. Front-loaded with the action and the default. Slight fragmentation — the scope requirement dangles at the end — but nothing is wasted.

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 create tool with a large nested event object and no output schema, the description covers the critical publish-safety path and date/timezone format but omits what the call returns (e.g. the created event's identifier) and any guidance on the optional nested fields. Adequate but with clear gaps given the schema's depth.

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 50%, and confirm_publish already carries a schema description nearly identical to the prose. The description does add genuine semantics the schema lacks: timezone must be IANA and dates must be ISO with offsets — real value for the nested event fields. But it says nothing about the many optional nested fields (address, ends_at, show_on_page, ticket_url, etc.), so the 50% coverage gap is only partly filled.

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 specific verb+resource ("Create a calendar event") that matches the name and title, and it immediately adds scope detail (defaults to draft). It doesn't explicitly name siblings like event_update or event_cancel to delineate boundaries, but the create verb is unambiguous against those names.

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?

It gives a real when-to-do-what rule: default is draft, and publishing requires asking the person first and passing confirm_publish: true. It also states the required API key scope. Missing is any explicit statement about when to use event_update or event_cancel instead, but for a create tool the guidance is solid.

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