Skip to main content
Glama

Build an iCalendar event

bpj_build_calendar_event
Read-onlyIdempotent

Create an importable ICS calendar event from its title, start time, and duration.

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>",
      "uid": "<uid>",
      "start": "<start>",
      "created": "<created>",
      "durationMinutes": "<durationMinutes>"
    },
    "name": "bpj_build_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
startYes
createdYes
summaryYes
durationMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive and closed-world, so the safety profile is covered; 'create' here is consistent with a pure string builder because it says 'importable ... from'. The description adds the fact that output is ICS-importable, but omits what is actually returned (raw ICS text), line-ending/timezone handling, and that no calendar is contacted.

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?

A single front-loaded sentence with no filler, so the core action is immediately visible. It is arguably too terse for a five-required-parameter tool, but nothing in it is wasted.

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?

For a tool with five mandatory inputs, no output schema, and no annotation detail on the result, the description leaves important pieces unexplained: the two required identifiers and what the caller receives back. An agent could not call this correctly from the description alone without reading the schema.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, yet it only accounts for three of the five required fields (title, start, duration) by paraphrase. The mandatory 'uid' and 'created' inputs are never mentioned in the description, and no format expectations beyond the field titles are supplied.

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 product: 'Create an importable ICS calendar event', with the source inputs named. That is enough to separate it from the sibling utilities, which are all analysis/formatting helpers rather than calendar builders. It stops short of 5 because it never says the result is a text blob rather than a stored event.

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?

There is no when-to-use or when-not-to-use guidance and no mention of prerequisites. Nothing tells the agent whether this should be called to produce a downloadable artifact versus writing to a calendar service, nor which sibling to prefer for timestamp 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.