MCP OpsBridge

calendar_create_event

Creates a calendar event with summary, start/end times, and optional attendees. Requires approval, and uses ISO 8601 timestamps.

Instructions

Create a calendar event with optional attendees (requires approval)

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": {
      "summary": "<summary>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "calendar_create_event"
  }
}

Input Schema

Name	Required	Description	Default
`summary`	Yes	Event title
`end_time`	Yes	End time (ISO 8601)
`attendees`	No	Attendee email addresses
`start_time`	Yes	Start time (ISO 8601)
`calendar_id`	No		primary
`description`	No	Event description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds a key behavioral trait: 'requires approval', which is not apparent from the schema. However, it omits critical details such as return value, rejection behavior, or what the approval process entails, leaving significant ambiguity.

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 a single, tightly crafted sentence that clearly states the core action and a notable constraint. It is front-loaded with the verb and resource, and contains no filler or redundant wording.

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?

Despite the tool's six parameters and lack of output schema, the description provides no details about return values, calendar_id behavior, or the approval workflow. It leaves the agent largely guessing about what happens after invocation. The description is too sparse to be considered complete for this tool's complexity.

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 83%, with only calendar_id lacking a description. The description's 'optional attendees' simply restates the schema's optionality without adding new meaning. It does not clarify calendar_id defaults or time formats beyond what the schema already conveys, so it adds minimal value.

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 uses a specific verb ('Create') and resource ('calendar event'), immediately distinguishing it from sibling tools like calendar_update_event or calendar_delete_event. The mention of 'optional attendees' adds further specificity, making the tool's purpose unmistakable.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The only hint is 'requires approval', but this is not elaborated and does not explain when approval is needed or suggest alternative tools.

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