Helium - Student Planner

Import an .ics file

import_ics

Save an .ics calendar file's entries to Helium, all at once: as assignments in a class already in Helium (uncategorized and ungraded, since a calendar has only titles, dates, and times), or as events. Repeating entries are expanded, and cancelled ones left out. Adds to the account; changes nothing already there. Importing the same file twice adds its entries twice. preview_import_ics shows what it would create.

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": {
      "ics": "<ics>"
    },
    "name": "import_ics"
  }
}

Input Schema

Name	Required	Description	Default
`ics`	Yes	The calendar, as the .ics file's text, unchanged.
`class_id`	No	The class whose assignments the entries become (an id from list_classes, or from what import_term returned). Unset imports them as events.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds the operationally important facts: the import is purely additive ('changes nothing already there'), it is NOT idempotent and re-importing duplicates entries, repeating entries are expanded, cancelled entries are dropped, and data is lossy (uncategorized, ungraded). This is exactly the behavioral context an agent needs before a mutation.

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?

A single tight block that front-loads the action and mode split, then layers the behavioral caveats. Every clause carries distinct information; nothing is redundant or padded.

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?

With an output schema present and annotations covering the safety profile, the remaining burden is explaining mutation semantics and alternatives, both of which are addressed. An agent can call this correctly, including avoiding accidental duplicate imports, from the description alone.

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%, so both parameters are already documented, including that unset class_id means events. The description adds real value by explaining the consequence of setting class_id (assignments become uncategorized and ungraded) and why (a calendar carries only titles, dates, and times), but it does not add format or validation detail 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?

The description names a specific verb and resource ('Save an .ics calendar file's entries to Helium') and immediately disambiguates the two output modes: assignments in an existing class, or events. It also distinguishes itself from preview_import_ics, so an agent can tell the import apart from the preview without inspecting schemas.

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

Usage Guidelines4/5

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

It gives a clear routing cue to preview_import_ics ('shows what it would create') and explains which mode applies based on class_id ('Unset imports them as events'). It stops short of an explicit when-not-to-use statement or a recommended preview-first workflow, so it is strong context rather than a complete decision rule.

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

All Helium - Student Planner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.