Skip to main content
Glama

Расписание через ЕЛК

elk_get_schedule
Read-onlyIdempotent

Fetches a student's HSE class schedule for the next N days from the personal cabinet API, including online class links and working from any network.

Instructions

Расписание занятий студента через API Единого личного кабинета (lk.hse.ru/api/get-myschedule) — включая ссылки на онлайн-пары. Работает из ЛЮБОЙ сети (в отличие от RUZ, который доступен только из внутренней сети ВШЭ) — основной источник расписания.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "elk_get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysAheadNoНа сколько дней вперёд от сегодня

Output Schema

NameRequiredDescriptionDefault
daysYesДни с занятиями по порядку

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / days / items / properties / lessons / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / auditorium / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / auditorium / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / begin_time / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / begin_time / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / building / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / building / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / end_time / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / end_time / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / lecturer / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / lecturer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / lesson_type / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / lesson_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / parent_schedule / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / parent_schedule / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / url1 / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / url1 / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / url1_description / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / url1_description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / url2 / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / url2 / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / days / items / properties / lessons / items / properties / url2_description / $ref
      Removed value: -"#/properties/days/items/properties/lessons/items/properties/name"
    • addedOutput schema / properties / days / items / properties / lessons / items / properties / url2_description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: the upstream endpoint, network reachability compared to RUZ, and that returned entries carry online-class links. It stops short of noting caching, rate limits, or freshness of the data.

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 dense sentence plus a parenthetical contrast: purpose first, then the network reachability differentiator, then the source-of-truth claim. No filler, nothing to trim.

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 one optional parameter at full schema coverage, full annotations, and an output schema that explains return values, nothing an agent needs before calling is missing. The network-reachability caveat is the one piece of non-structured knowledge that matters, and it is present.

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% for the single optional daysAhead parameter, including default, min and max, so the schema carries the semantics. The description says nothing about the window parameter or its bounds, which is acceptable at full coverage but adds no value.

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?

Names a specific verb+resource (student class schedule) and pins the exact backing API (lk.hse.ru/api/get-myschedule), plus notes it includes online-class links. It explicitly distinguishes itself from RUZ, so an agent can separate it from the sibling read tools without opening a 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?

"Работает из ЛЮБОЙ сети (в отличие от RUZ...)" plus "основной источник расписания" gives a clear selection rule: prefer this for schedule data unless on the HSE internal network. No explicit when-not-to-use is stated, and no sibling tool name in the provided list is called out as an alternative.

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