Skip to main content
Glama

Create personal calendar event

bb_create_calendar_event

Create a personal Blackboard calendar event with a title, start and end times, location, and notes; write access and explicit confirmation are required.

Instructions

Create an event on your personal Blackboard calendar. Requires BB_ALLOW_WRITES=1 and confirm:true.

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": {
      "title": "<title>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "bb_create_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
confirmNo
endDateYesISO 8601 timestamp
locationNo
startDateYesISO 8601 timestamp
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, non-idempotent write, so the description's added value is the gating requirements: BB_ALLOW_WRITES=1 and confirm:true. That is real operational context an agent would otherwise discover only by failing. It still does not say what error occurs when the gate is closed or whether retries create duplicates (relevant given idempotentHint=false).

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?

Two short sentences, front-loaded with the action and followed by the blocking precondition. Every clause carries information, and there is no filler.

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?

For a 6-parameter mutation with no output schema, the description covers purpose and the write gate, so an agent can call it correctly. Remaining gaps are timezone/date handling and what the call returns (e.g., an event id), which are useful but not blocking.

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 only 33%, with just startDate and endDate documented as ISO 8601. The description compensates partially by stating that confirm:true is required, which the schema does not (confirm is listed as an optional boolean), but title, location, and description semantics are left entirely to the schema.

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 gives a specific verb and resource ("Create an event") scoped to "your personal Blackboard calendar", which cleanly separates it from the update/delete calendar siblings by verb alone. It does not explicitly name those siblings, but the create-vs-update-vs-delete distinction is unambiguous.

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?

It states the precondition for use (writes enabled, confirm:true) but gives no guidance on when to prefer this over related tools or when not to call it. Usage is implied by the purpose rather than spelled out.

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