Skip to main content
Glama

Раздел ЕЛК

elk_get_section
Read-onlyIdempotent

Reads a specified HSE personal cabinet section—profile, login history, tasks, thesis, portfolio, internships, or scholarship requests—and returns its data as text.

Instructions

Один из разделов Единого личного кабинета (lk.hse.ru и его порталы) по имени section. profile — страница профиля /profile текстом и ссылками (ФИО, контакты); для рейтинга, GPA и группы есть elk_get_academic_data. login_history — история входов: дата, действие, IP, местоположение, устройство (проверка безопасности аккаунта; offset — пагинация). tasks — задачи пользователя (/task); поля задачи вживую не подтверждены, ответ как есть (limit — максимум задач). dpo_programs — программы ДПО, на которые подана заявка, со statusLabels; у остальных студентов пусто. antiplagiat — сколько проверок в Антиплагиате обрабатывается, завершено и подано. course_evaluation — периоды СОП («Оцени свои курсы») и заполнена ли анкета. thesis — статус ВКР/КР: тема, заимствования, оценка, рецензия; пусто, если тема не зарегистрирована. portfolio — электронное портфолио (достижения, влияют на повышенную стипендию), текстом. internships — заявки на практику. scholarship_history — история заявок на повышенную стипендию; пусто, если заявок не было. Все разделы только читаются: подача заявок не реализована.

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": {
      "section": "<section>"
    },
    "name": "elk_get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoТолько для tasks: максимум задач (по умолчанию 500)
offsetNoТолько для login_history: смещение для пагинации (по умолчанию 0)
sectionYesКакой раздел прочитать

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. First observedv0.1.1

TDQS

A4.1/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. The description adds genuinely new behavioral detail: write operations (submission of requests) are not implemented, several sections return empty under stated conditions, and task fields are 'не подтверждены' so output is returned as-is. This is useful beyond the annotations, though it doesn't cover rate limits or pagination limits of the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose followed by a dense but purposeful per-section enumeration; every clause about a section adds meaningful semantics. It is a single long paragraph that would read better as a list, but nothing is wasted.

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?

For a polymorphic tool with no output schema, the description carries the burden well by explaining what each section returns, which fields to expect, and empty-result conditions. A few sections ('ответ как есть') remain vague about exact shape, keeping it just under a 5.

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% and the schema already documents that limit applies only to tasks and offset only to login_history. The description restates these constraints (max tasks, offset pagination) without adding format or syntax detail beyond the schema, so the baseline of 3 applies.

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+resource (read a named section of the Unified Personal Cabinet) and enumerates every section with its concrete contents. It actively distinguishes itself from the sibling elk_get_academic_data for rating/GPA/group.

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?

Repeatedly routes the agent: 'для рейтинга, GPA и группы есть elk_get_academic_data', and each section note frames its purpose (login_history for security checking, portfolio for stipend achievements). It lacks an explicit 'when not to use this whole tool' or routing to other siblings like elk_get_user_info, so it stops short of 5.

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