Skip to main content
Glama

Read the calendar subscription

calendar_subscription_get
Read-onlyIdempotent

Retrieves your own calendar feed subscription for a flat so you can give the user a feedUrl to add to their calendar app. Returns null when no feed is active yet.

Instructions

Read the caller's own calendar feed subscription for the flat. Returns subscription { feedUrl, createdAt, updatedAt }, or subscription null when no feed is active; then call calendar_subscription_create. Use it to give the user a URL to add to a calendar app; to list the events themselves use events_list. Read-only; any member may call it, and each member has their own feed. 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_get"
  }
}

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. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior, but the description adds important context: the exact return shape, the null-state follow-up action, per-member feed ownership, and the sensitive nature of feedUrl. The security warning about never posting the token in chat, notes, or logs is material behavior an agent could not infer from annotations alone.

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 front-loaded with the tool's purpose and return behavior, then follows with the null-case action, alternative tool, and security constraint. Every sentence contributes useful operational or safety context, with no redundant wording.

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?

Although there is no output schema, the description explains the return object fields and the null case. It also covers the security handling of feedUrl and the member-scoped nature of the feed, which is enough for an agent to invoke and handle the result 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 already documented in the schema with its pattern and omission rule. The description does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: reading the caller's own calendar feed subscription for the flat. It clearly distinguishes this from calendar_subscription_create and events_list, so an agent can identify the tool's scope without opening sibling schemas.

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?

It explicitly says to call calendar_subscription_create when the result is null, and to use events_list when the goal is listing events themselves. It also clarifies that each member has their own feed, which is essential context for choosing this tool correctly.

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