Skip to main content
Glama
Sign In

Helium - Student Planner

by io.github.HeliumEdu
OverviewDiscussionsAdmin

Preview an .ics import

preview_import_ics
Read-onlyIdempotent

Check an .ics calendar file against what Helium accepts, without saving anything: how many assignments (in a class already in Helium) or events its entries would become. Returns the problem if Helium can't 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": {
      "ics": "<ics>"
    },
    "name": "preview_import_ics"
  }
}

Input Schema

NameRequiredDescriptionDefault
icsYesThe calendar, as the .ics file's text, unchanged.
class_idNoThe class whose assignments the entries become (an id from list_classes, or from what import_term returned). Unset imports them as events.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real behavior: entries become assignments when a class is supplied and events otherwise, and an unimportable file yields a problem report rather than an exception. It doesn't discuss size limits or partial-import semantics, which is the remaining gap.

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?

One compact sentence, front-loaded with the dry-run guarantee and the return content. Nothing is repeated from the title or schema, and no filler remains.

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

Completeness4/5

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

With a full output schema and rich annotations, this description supplies enough for correct invocation: what the input is, what the class_id toggle does, and what failure looks like. Only edge cases such as very large files or unparseable text handling are unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds a constraint the schema doesn't: assignments only count when their class already exists in Helium, and omitting class_id switches the entries to events. That is genuine semantic value beyond the field descriptions.

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 and resource ("Check an .ics calendar file against what Helium accepts") plus the distinguishing dry-run constraint ("without saving anything") and the output content (counts of assignments or events). That combination separates it from import_ics without needing to name it.

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?

The phrase "without saving anything" makes the use case clear: validate before committing, since the saving counterpart is import_ics. It stops short of explicitly routing an agent that is ready to import to that other tool, or pointing term-file previews at preview_import_term.

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 toolsInspect
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.

Resources