Skip to main content
Glama

event_brief_to_ics

Read-onlyIdempotent

Create a real iCalendar file from a brief with Start: YYYY-MM-DD HH:MM IANA/Zone, Duration: N minutes, Title: text, optionally preceded by a Markdown heading. Resolves timezone to UTC; refuses ambiguous/nonexistent DST times. createdAt must be UTC ISO seconds. Does not add any calendar event. Official documentation: https://creora.darwin.so/providers/files/docs

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": {
      "eventBrief": "<eventBrief>",
      "createdAt": "<createdAt>"
    },
    "name": "event_brief_to_ics"
  }
}

Input Schema

NameRequiredDescriptionDefault
createdAtYes
eventBriefYes

Output Schema

NameRequiredDescriptionDefault
artifactsYes
sheetNamesYes
sourceSha256Yes
externalWritesYes

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 already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavior: timezone resolution to UTC, rejection of ambiguous or nonexistent DST times, and the fact that no calendar event is created as a side effect. It stops short of describing output contents or size limits, keeping it at a solid 4 rather than 5.

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?

The purpose is front-loaded and the following clauses each add distinct information (input format, timezone/DST policy, createdAt constraint, side-effect disclaimer). The trailing documentation URL is slightly promotional but harmless.

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?

With only two parameters, an output schema present, and rich annotations, the description supplies everything needed to call the tool correctly: input grammar, timestamp format, and DST failure conditions. Only minor gaps (size limit, output file location/return) remain, and the output schema can cover the latter.

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 description coverage is 0%, so the description must carry both parameters, and it does: eventBrief is spelled out as Start/Duration/Title lines with an optional Markdown heading, and createdAt is clarified as 'UTC ISO seconds'. It does not mention the 131072 maxLength, so the schema still holds undisclosed constraints.

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?

States a specific verb+resource ('Create a real iCalendar file from a brief') and immediately enumerates the brief's expected format, so an agent knows exactly what the tool produces. Siblings (csv_to_xlsx, markdown_to_pdf, etc.) are unrelated conversions, so no explicit differentiation is needed, but the description also doesn't route the agent among them.

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?

'Does not add any calendar event' is a useful exclusion, and 'refuses ambiguous/nonexistent DST times' signals a failure mode. However, there is no explicit statement of when to prefer this over another conversion path, nor prerequisites beyond the input format.

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