Skip to main content
Glama

Create the calendar subscription

calendar_subscription_create
Idempotent

Create a flat calendar feed that calendar apps can subscribe to; use it when no active subscription exists so members can view events.

Instructions

Create the caller's own calendar feed for the flat, so a calendar app can subscribe to the flat's events. Use it when calendar_subscription_get returns subscription null; to read an existing feed use calendar_subscription_get, to replace a leaked URL use calendar_subscription_rotate. Safe to repeat: if a feed is already active it is returned unchanged; after calendar_subscription_revoke it creates a fresh feed with a new URL. Any member may call it; it notifies nobody. Returns subscription { feedUrl, createdAt, updatedAt }. feedUrl contains a secret token that grants read access to the flat's events, so show it only to the user and never post it in chat, notes or logs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_subscription_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial meaning beyond the annotations: idempotent behavior is spelled out concretely ('if a feed is already active it is returned unchanged'), the post-revoke outcome is described, and the side-effect profile ('notifies nobody') is disclosed. The secret-token warning ('grants read access... never post it in chat, notes or logs') is important handling guidance the annotations do not convey.

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?

Front-loaded with purpose, then trigger, then behavior, then return shape and security note – a logical order with no throwaway content. Minor redundancy from mentioning calendar_subscription_get twice in the same clause, and the security warning could be its own sentence, but overall it is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming the return shape (subscription { feedUrl, createdAt, updatedAt }). Combined with idempotency, post-revoke semantics, permission scope and the token sensitivity warning, an agent has everything needed to call and handle this tool correctly.

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 100% and the single optional wgCode parameter is fully documented in the schema, so the baseline of 3 applies. The description never mentions wgCode or the single-flat default, adding no meaning beyond the schema.

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?

States a specific verb+resource ('Create the caller's own calendar feed for the flat') with its purpose ('so a calendar app can subscribe to the flat's events'), which cleanly separates it from calendar_subscription_get and calendar_subscription_rotate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ('Use it when calendar_subscription_get returns subscription null') and names both alternatives with their conditions: get for reading an existing feed, rotate for a leaked URL. Also states who may call it ('Any member may call it').

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