holiplan

Overview Schema Source Related Servers Discussions Admin

export_ics

Export a holiday planning ledger as an .ics calendar file to save and import into calendar apps, covering school and public holidays, leave windows, and optional deadlines.

Instructions

The ledger as an .ics calendar file the user can import.

Returns file contents -- tell the user to save it and import it.

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": {
      "ledger": "<ledger>"
    },
    "name": "export_ics"
  }
}

Input Schema

Name	Required	Description	Default
`ledger`	Yes
`include_deadlines`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important non-obvious trait: the tool returns file *contents* rather than writing a file, and the user must save/import it. However, it says nothing about whether include_deadlines changes the output, whether the ledger is mutated, or any size/permission constraints.

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?

Two short sentences, front-loaded with what the tool produces and followed by the one operational instruction the agent needs. Nothing is redundant or padded.

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

Completeness3/5

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

An output schema exists, so return-value shape need not be described, and the ledger parameter is a loose nested object. Still, for a two-parameter export tool the description omits the meaning of include_deadlines and any note on ledger contents, leaving a real gap.

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% and neither of the two parameters is mentioned. The description does not explain what the 'ledger' object should contain or what toggling 'include_deadlines' (default true) does to the exported calendar, leaving both parameters entirely undocumented across schema and description.

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 names the resource (the ledger) and the output artifact (.ics calendar file the user can import), so the purpose is unambiguous. It does not differentiate itself from siblings like summarise_plan or list_deadlines, but no sibling overlaps this export behavior, so the distinction is implicit.

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 statement of when to use this versus alternatives (e.g., list_deadlines for reading deadlines in-app versus exporting them). The only guidance is post-invocation handling ('tell the user to save it and import it'), which is instruction for the agent's response, not selection guidance.

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

Deploy Server