booking_chest

by dsddet

Overview Schema Source Related Servers Discussions Admin

Python

Remote

save_ics_feed

Subscribe to external ICS calendar feeds to integrate events from other calendars into your schedule.

Instructions

Subscribe to external ICS calendar feeds.

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": {
      "urls": "<urls>"
    },
    "name": "save_ics_feed"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	List of ICS feed URLs
`read_only`	No	Whether feeds are read-only (default: true)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 18, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not indicate whether subscribing requires special permissions, whether it mutates state (e.g., creates a stored subscription), what happens on failure (e.g., invalid URL), or if there are rate limits. 'Subscribe' implies a persistent change, but this is left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At 5 words, the description is extremely concise. However, it is too terse for a tool with 2 parameters and a persistent effect; additional context would be justified. The front-loading of the purpose is good, but the brevity comes at the cost of completeness.

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?

Given that there is an output schema (not shown but confirmed present), the description need not explain return values. However, the tool handles external URL subscriptions, which implies error handling (invalid URLs, network issues) and side effects (data persistence). The description omits all of this, making it incomplete for practical usage.

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 100%, so the schema already documents both parameters. The description adds no further meaning beyond the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Subscribe to external ICS calendar feeds,' which clearly identifies the verb (subscribe) and resource (ICS feeds). However, it does not distinguish this tool from the sibling tool `check_ics_feed`, which also deals with ICS feeds, so the differentiation is missing.

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 like `check_ics_feed`. There is no mention of prerequisites (e.g., needing a feed URL format), when not to use it, or what the subscription entails in terms of ongoing behavior (e.g., polling).

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

Deploy Server