Helium - Student Planner

Import a term

import_term

Save a term's assignments, events, classes, meeting times, and grading categories to Helium, all at once: as a new term, or into one already in Helium. Adds to the account; changes nothing already there. preview_import_term 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": {
      "plan": "<plan>"
    },
    "name": "import_term"
  }
}

Input Schema

Name	Required	Description	Default
`plan`	Yes	A term's assignments, events, classes, schedules, and grading, read from the syllabi of every class in the term, for a new term or one already in Helium. Dates and times are local: Helium places them in the time zone set in the student's Helium account.
`allow_duplicates`	No	Import even if the new term (same title and dates) or a class (same title, in an existing term) is already in Helium.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, it discloses that the operation is purely additive — 'Adds to the account; changes nothing already there' — which reinforces destructiveHint=false with a concrete guarantee about existing data. It stops short of describing duplicate handling (non-idempotent re-imports), though the allow_duplicates parameter in the schema documents that behavior.

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 tight sentences with no filler: the first front-loads purpose and the dual create/append mode, the second states the additive guarantee and points at the preview sibling. Every clause carries information an agent needs.

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 100% schema coverage, an output schema, and annotations covering safety, the description supplies the remaining decision-critical context: purpose, target mode, additive semantics, and the preview counterpart. The only omission is any mention of duplicate detection or time-zone handling, both of which the schema already explains in depth.

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 is 3, but the description adds real meaning by explaining the two branches of the plan.term union (a new term versus one already in Helium) and framing the payload as term-wide data aggregated from every class syllabus. It does not discuss allow_duplicates or sizing limits, which remain schema-only.

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 concrete verb (save/import) and enumerates the exact resource payload: a term's assignments, events, classes, meeting times, and grading categories. It also states both target modes (new term vs. an existing one in Helium) and names the sibling preview_import_term, so an agent can act without opening the schema.

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 clear context for when to use it (bulk-importing a whole term's data at once, either creating a term or appending to an existing one) and routes the agent to preview_import_term first. It does not explicitly rule out import_ics or spell out a preview-then-commit workflow requirement, so no exclusion guidance is present.

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.